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
mshinwell 3:32 PM
I'm looking at another interesting allocation test failure (down to the last two I think)
3:33
There is a functor from another library applied in the current unit and the result is included (edited)
3:33
Then a function calls one of the functions from that functor
3:33
Closure has a projection directly from the symbol of the other unit at the application site
3:34
We end up with the function having a free variable for the callee. The free variable is bound, prior to the lambda, as part of the include mechanism to the field projection.
3:34
Presumably if cross-library inlining were enabled everything would be ok, but when it's off, this causes a closure allocation
No description provided.
The text was updated successfully, but these errors were encountered: