[cppyy] Consider Python int and float for make_unique optimization
#20977
+8
−3
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.
The
std::make_uniquefunction is Pythonized to avoid unnecessary code generation by TClingCallFunc, which might also go wrong (as reported in GitHub issue #19122).There is a fallback to calling the original
make_uniquefor builtin types (introduced in [1]), but we don't need that if we know the builtin type can be readily used in theunique_ptrconstructor, as is the case forintandfloat.Hence, this commit suggests to not use the fallback for
intandfloat, which also closes #19122 because no wrapper code has to be generated anymore.[1] wlav/cppyy@62a97c9