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

Execute TypeResolver before VariableUsageResolver #1277

Merged
merged 3 commits into from
Aug 14, 2023
Merged

Conversation

oxisto
Copy link
Member

@oxisto oxisto commented Aug 9, 2023

This PR moves the execution order of the TypeResolver before the VariableUsageResolver and CallResolver. This should help clean up the type manager code that deals with record / type hierachies in a better way.

@oxisto oxisto force-pushed the move-type-resolver branch 6 times, most recently from 478cd01 to e67b5cb Compare August 10, 2023 13:55
@oxisto oxisto marked this pull request as ready for review August 10, 2023 14:10
@oxisto oxisto force-pushed the move-type-resolver branch 2 times, most recently from ada673a to 050abd0 Compare August 11, 2023 08:51
This PR moves the execution order of the `TypeResolver` before the `VariableUsageResolver` and `CallResolver`. This should help clean up the type manager code that deals with record / type hierachies in a better way.
oxisto and others added 2 commits August 11, 2023 14:59
…rapState.kt

Co-authored-by: KuechA <31155350+KuechA@users.noreply.github.com>
@sonarcloud
Copy link

sonarcloud bot commented Aug 11, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

81.3% 81.3% Coverage
0.0% 0.0% Duplication

@oxisto oxisto merged commit 607b498 into main Aug 14, 2023
3 checks passed
@oxisto oxisto deleted the move-type-resolver branch August 14, 2023 09:41
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.

2 participants