Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not check assembly symbols equality by DefinitionRange and name #4662

Merged
merged 4 commits into from
Jun 12, 2018

Conversation

auduchinok
Copy link
Member

@auduchinok auduchinok commented Apr 2, 2018

Currently, assembly symbols have startup definition range and are considered equal when LogicalName equals.
We should not check this range for assembly symbols, as a proper check is done just before.
Fixes #4658.

Assembly symbols have startup definition range and considered equal.
Fixes dotnet#4658.
@auduchinok auduchinok force-pushed the assembly-symbols-defnEq-fix branch from ff6269b to 0c7c3bc Compare April 2, 2018 10:14
@auduchinok
Copy link
Member Author

auduchinok commented Apr 2, 2018

@dsyme Is it a good idea to have such definition ranges for symbols and rely on it this way at all?
What would be a better way to check that a symbol is from an assembly and we should not try comparing declaration ranges?

@auduchinok auduchinok force-pushed the assembly-symbols-defnEq-fix branch from ec8bd98 to 2949028 Compare April 2, 2018 15:44
@vasily-kirichenko
Copy link
Contributor

Any plans to merge this? It's ready for a month.

@cartermp cartermp requested a review from dsyme May 27, 2018 21:48
@dsyme
Copy link
Contributor

dsyme commented May 29, 2018

We can merge this but we should first re-test once IDE tests are re-enabled I suppose

@dsyme
Copy link
Contributor

dsyme commented May 29, 2018

cc @KevinRansom

@KevinRansom KevinRansom merged commit 3846384 into dotnet:master Jun 12, 2018
auduchinok added a commit to auduchinok/fsharp that referenced this pull request Mar 21, 2019
…otnet#4662)

* Do not check assembly symbols equality by DefinitionRange and name

Assembly symbols have startup definition range and considered equal.
Fixes dotnet#4658.

* Add test for equality of entities from assemblies with the same name

* Add checks for range0 and rangeCmdArgs ranges

* Do not run new tests on netcoreapp2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants