On Tue, 17 Jan 2017, Daniel Shahaf wrote:

> Peter Stephenson wrote on Tue, Jan 17, 2017 at 18:36:06 +0000:
> > I think this is the right way of doing it as the explicit
> > path should continue to override the more vague autoload with no path
> > indicated, and this is safer in case some code decides it needs a
> > function and inadvertently resets the path the user carefully decided to
> > give the function.
>
> Suppose $^fpath/foo/bar(N) has two matches, how do I explicitly autoload
> the second one?  I.e., how do I disambiguate «autoload foo/bar» (with no
> leading slash) to load a particular copy of foo/bar?

How does any of this interact with searching for functions inside files
built with zcompile?

(Does zcompile even support having a function name that contains a slash?)