(use subdir/file) doesn't actually make the stuff in that file accessible. I assume this is because it's imported in the name "subdir/file" rather than "file", and trying to do subdir/file/foo results in the resolver looking for a module name subdir, which doesn't exist.

Expected behaviour is for the file to be imported under the name file -- i.e. the path stem. Seems to be a trivial fix.

Admittedly this was before the path resolving changes, and I haven't tested that this bug still exists afterwards. There's no obvious behaviour for it to have been fixed, though.