Skip to content
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

Extract object_mixin_data management from object_mutation #58

Open
iboB opened this issue Mar 19, 2023 · 0 comments
Open

Extract object_mixin_data management from object_mutation #58

iboB opened this issue Mar 19, 2023 · 0 comments
Labels
performance gotta go fast

Comments

@iboB
Copy link
Owner

iboB commented Mar 19, 2023

object::clear_mixin_data is noexcept, but relies on an noexcept(false) destructor. It should never throw in the given case, but still the compiler will generate calls to std::terminate there. It is possible to create a class basic_object_mutation which provides alloc/dealloc/destroy functions for mixin data. I can have a noexcept destructor and can be used by both object_mutation and clear_mixin_data.

@iboB iboB added the performance gotta go fast label Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance gotta go fast
Projects
None yet
Development

No branches or pull requests

1 participant