-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: only executables should choose a global allocator #301
Conversation
FWIW I would normally want to see profiling before opting-in to any allocator change, but I don't want to get bogged down in that discussion for now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sinilarly to your comment about opting-in a global allocator, I would expect profiling results before justifying removal. I believe Jacqui had good reasons bringing in the past and if there is a performance gain, and it is non-negligible, it may be worth considering alternative options?
Especially as there is little point in having both type1 / type2 live concurrently, hence the issues faced in the past by Brendan and possibly you now as well shouldn't be actually happening once we get to a more evolved state.
If we make it the default on zero-bin side then it should be fine though, but full removal should wait IMHO.
Thanks for the review,
I don't think PR constitutes removal - it's changing who is specifying the global allocator (which is not changing) - perhaps your comment belongs in #302? There's a bit of nuance in this PR: each executable has a global allocator, and I count 5 executables in the repo:
I expect only To summarize:
What are the next steps to approve this PR? |
Right it probably have been better suited within #302, I was just sharing concerns about removing |
This is general rust wisdom, and it prevents me linking two different versions of
evm_arithmetization
in #275