You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The book "Hands-on design patterns and best practices with Julia" recommends to employ import when a functionality is being extended, otherwise to employ using by default. This is so far the way I have followed.
The text was updated successfully, but these errors were encountered:
Keep in mind that import and using have subtly different semantics. I think if we follow the rule that all imports have to be explicit (i.e. no using ) then we might just go the full way and prohibit import altogether (and use explicit name resolution for method definitions).
Sorry, my comment was partially eaten by the md formatter. Where it says 'i.e. no using' it should have said 'i.e. no using modulename' (I included modulename in < and > which apparently made it disappear).
The book "Hands-on design patterns and best practices with Julia" recommends to employ
import
when a functionality is being extended, otherwise to employusing
by default. This is so far the way I have followed.The text was updated successfully, but these errors were encountered: