Make SimpleTypeName
support types defined inside unnamed constants
#91
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.
Checklist
Description of Changes
I just discovered that if you have a type defined inside an unnamed constant like
then
type_name::<<Foo as A>::T>()
will becrate::_::Bar
. Such code is common with macros because you can import stuff without polluting the surrounding namespace.However
syn
does not support parsing such type names 😕 Stripping the::_
part is probably the easiest solution.