top-level ids shouldn't need a path mapping if they are children of baseUrl

[ben hockey]

transferred from ​http://bugs.dojotoolkit.org/ticket/12672#comment:138

require({
    baseUrl: '/abs/path/to/base'
},
['init'], function (init) { 
    // ... 
});

tries to fetch 'init' from '/abs/path/to/init' but i think it should be 'abs/path/to/base/init'

adding a path mapping fixes it:

require({
	baseUrl: '/abs/path/to/base',
	paths: {
		init: 'init'
	}
},
['init'], function (init) { 
	// ... 
});

but i would have expected that this mapping wouldn't be necessary

[Rawld Gill]

top-level modules are siblings to the dojo directory. baseUrl is assumed to be the dojo directory. So /abs/path/to/base is dojo, /abs/path/to/init is the sibling. This is expected behavior.

[ben hockey]

this is unfortunately inconsistent with requirejs which imo uses a more intuitive approach. this is definitely a dojo-specific way to interpret baseUrl