Add package name when unambiguous classes with same name in different package #3223
Conversation
This file contains 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
maximedezette
force-pushed
the
unambiguous-representation-same-class-name-in-different-packages
branch
from
99a792a
to
4055fdd
Compare
maximedezette
force-pushed
the
unambiguous-representation-same-class-name-in-different-packages
branch
from
4055fdd
to
2083929
Compare
scordio
force-pushed
the
3.x
branch
2 times, most recently
from
301ca01
to
c730d18
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Check List:
UnambiguousRepresentationcomputes same output when types have same name but different packages #3084Following the contributing guidelines will make it easier for us to review and accept your PR.