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
A question is whether this was overlooked or is there a serious reason that specialization does not visit local methods. Btw, this bit us while working on https://github.com/nicolasstucki/specialized/.
The text was updated successfully, but these errors were encountered:
@paulp said:
This was just brought up by rex kerr as well. I feel safe in saying there's no reason not to specialize local methods; quite the opposite, they should be prioritized because the limited visibility means they won't be subject to most of the problems which plague specialization.
@VladUreche said:
A little digging into this bug shows there's an undocumented assumption in specialization: normalized members (methods whose type parameters are specialized) should always belong to classes. This assumption is visible in the info transformer, which only matches ClassInfoTypes and in the tree transformer which only creates empty bodies for methods inside ClassDefs.
It shouldn't be impossible to undo this assumption, but it may take some hacking to have a PR ready.
A question is whether this was overlooked or is there a serious reason that specialization does not visit local methods. Btw, this bit us while working on https://github.com/nicolasstucki/specialized/.
The text was updated successfully, but these errors were encountered: