Support ReSharper builtin for type name #709
Merged
+4
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 function
type_nameis very compiler-dependent, its implementation already contains preprocessor branches for Clang, GCC and MSVC. In ReSharper (it's the plugin for Visual Studio and the language engine used in CLion IDE and Rider) there is the special builtin__rscpp_type_namefor getting type name. This builtin is more efficient than extracting text from function signature on the one hand and avoids the need to exactly emulate macros__PRETTY_FUNCTION__/__FUNCSIG__in all compilers on the other hand.The similar patch was accepted in another popular open-source C++ library magic_enum few years ago.