-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
From() without a new allocation #85
Comments
Sounds reasonable. |
@dececx Do you want to write a PR? |
Note that this issue is still reasonable and could be fixed rather easily. For people reading this, the idea is that you'd avoid creating a new Bitset instance (which |
SignorMercurio
added a commit
to SignorMercurio/bitset
that referenced
this issue
Apr 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you think it would be reasonable to add something like:
It's basically
From()
without a new allocation. Escape analysis seems to force a heap allocation with the current From() and I'm trying to avoid it.The text was updated successfully, but these errors were encountered: