Support ReSharper C++ builtins for type/enumerator name #238
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.
In ReSharper C++ we have our own constexpr evaluation engine. However, getting enumerator or type name with
__PRETTY_FUNCTION__
hacks slows down perfomance of its on-the-fly code analysis. For example, resolving ofstd::array<int, magic_enum::enum_count<SomeEnum>()>
requires bruteforcing of all enum names in range[MAGIC_ENUM_RANGE_MIN, MAGIC_ENUM_RANGE_MAX]
leading to enormous number of template instantiations and constexpr calculations.Since upcoming 2023.1 version ReSharper has builtins, that can be used to get type name or enumerator name directly:
__rscpp_type_name<T>()
and__rscpp_enumerator_name(value)
. They greatly speed up evaluation of alln<T>()
andn<E, V>()
internal functions.