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
Sometimes I just depend on Lazy for Lazy.@forward, but the latter is already in MacroTools, although unexported.
Perhaps it would make sense to move it to this package "officially", deprecating Lazy.@forward. The functionality is not strongly tied to either package, but this would remove one dependency from those who just need this single macro.
The text was updated successfully, but these errors were encountered:
I'm down for that, but OTOH this will break code for users who are using both Lazy and MacroTools. So on the whole, I'm not sure that it's worth it... using MacroTools: @forward seems acceptable...
Sometimes I just depend on
Lazy
forLazy.@forward
, but the latter is already inMacroTools
, although unexported.Perhaps it would make sense to move it to this package "officially", deprecating
Lazy.@forward
. The functionality is not strongly tied to either package, but this would remove one dependency from those who just need this single macro.The text was updated successfully, but these errors were encountered: