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

Make public backing fields explicitly unscoped. #231

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

jesyspa
Copy link
Owner

@jesyspa jesyspa commented Jul 25, 2024

Previously, we maintained scoping information in the name. This was a bit messy; this PR changes the approach to not give them a scope at all.

We don't remove the special case on public scope yet, since that also impacts public properties.

Previously, we maintained scoping information in the name.  This was a
bit messy; this PR changes the approach to not give them a scope at all.

We don't remove the special case on public scope yet, since that also
impacts public properties.
@jesyspa jesyspa requested a review from francescoo22 July 25, 2024 12:38
@jesyspa jesyspa merged commit d363387 into formal-verification Jul 25, 2024
1 check passed
@jesyspa jesyspa deleted the backing-field-mangling branch July 25, 2024 15:07
jesyspa added a commit that referenced this pull request Jul 26, 2024
Previously, we maintained scoping information in the name. This was a
bit messy; this PR changes the approach to not give them a scope at all.

We don't remove the special case on public scope yet, since that also
impacts public properties.
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