Avoid a heap allocation on every legacy py::enum_ load #5860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
During development of #5800, I noticed that the native enum caster unnecessarily heap-allocates the fallback base caster if it needs to handle a load of a type that was exposed using the pre-v3
py::enum_rather thanpy::native_enum. Fix this.Since
enum_is a wrapper aroundclass_, a Python instance of a type exposed withenum_contains a [pointer to a] C++ enum object of appropriate type. It is therefore unnecessary to keep the type caster alive in order to preserve the referent of casts toconst EnumType&orEnumType*. The heap allocation previously used by the native enum caster was incurring a performance cost on loads without providing any reliability or clarity benefits.Suggested changelog entry:
Improve the performance of from-Python conversions of legacy pybind11 enum objects bound by
py::enum_.