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
We are actively working on the module system. The Smalltalk globals are already gone, extension methods are supported. However, because of implementation details there is no access from extension methods to module-local names yet.
Traditional extension methods contend against modularity, so we (@melkyades) are thinking about having a different implementation:
Extension methods could easily be stored in module objects instead of extended class' method dictionary (this would allow for more than one extension or extension version in the same class).
Extension methods could be accessed only through special syntax, explicitly stating the module where the extension is to be found. I.e. anArray math::asMatrix (where math is a module).
Could this allow to make the metalevel an extension module? i.e. anObject meta::class or anObject mirror::class
For now, we are ok with traditional extensions, but that might change in the future.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are actively working on the module system. The Smalltalk globals are already gone, extension methods are supported. However, because of implementation details there is no access from extension methods to module-local names yet.
Traditional extension methods contend against modularity, so we (@melkyades) are thinking about having a different implementation:
For now, we are ok with traditional extensions, but that might change in the future.
Beta Was this translation helpful? Give feedback.
All reactions