On Sunday, April 26, 2015 at 8:24:15 PM UTC+10, Scott Jones wrote: > > Yes, precisely... and I *do* want Julia to protect the user *in that case*. > If a module has functions that are potentially ambiguous, then 1) if the > module writer intends to extend something, they should do it *explicitly*, > exactly as now, and 2) Julia *should* warn when you have "using" package, > not just at run-time, IMO. > I have *only* been talking about the case where you have functions that > the compiler can tell in advance, just by looking locally at your module, > by a very simple rule, that they cannot be ambiguous. >
The issue is that, in the example I gave, the compiler can't tell, just by looking at your module, if that case exists. It has to look at everything else imported and defined in the users program, and IIUC with macros, staged functions and lots of other ways of defining functions that can become an expensive computation, and may need to be delayed to runtime. Cheers Lex > > Scott > >> >>>>> >>>>>
