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
Current behaviour is quite tricky and actually does not make much sense. We tell apart "native" constructors and "generated" ones (one that are created after unrolling union types) - for native we always took first constructor and make it primary, for generated we make primary only if there's one left (for some mysterious reason).
Actually there's no practical benefits from this.
Also, apart from other things it will lead for one less node lowering - and current trend is to lower node phase as much as possible.
The text was updated successfully, but these errors were encountered:
Current behaviour is quite tricky and actually does not make much sense. We tell apart "native" constructors and "generated" ones (one that are created after unrolling union types) - for native we always took first constructor and make it primary, for generated we make primary only if there's one left (for some mysterious reason).
Actually there's no practical benefits from this.
Also, apart from other things it will lead for one less node lowering - and current trend is to lower node phase as much as possible.
The text was updated successfully, but these errors were encountered: