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.

Sign up for GitHub

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

Jump to bottom

Consider switching to peverify-compat automatically when APTCA or similar attributes are used #22712

Closed
VSadov opened this issue Oct 16, 2017 · 1 comment
Closed

Consider switching to peverify-compat automatically when APTCA or similar attributes are used #22712

VSadov opened this issue Oct 16, 2017 · 1 comment
Assignees
@VSadov
Labels
Area-Compilers Bug Feature - Readonly References Readonly References Language-C#
Milestone
15.6

Comments

@VSadov
Copy link
Member

VSadov commented Oct 16, 2017 •
edited
Loading

There are cases where we can be sure that code needs to be peverify-compatible.

We should consider checking for that and automatically suppress optimizations that could interfere with that.

See for example bug - #22707
@VSadov VSadov mentioned this issue Oct 16, 2017
Closed
@VSadov VSadov self-assigned this Oct 16, 2017
@VSadov VSadov added this to the 15.later milestone Oct 16, 2017
@VSadov
Copy link
Member Author

VSadov commented Nov 9, 2017

Yes. we have short term a solution that we believe is the right balance between desire to use new features and produce code compatible with old verification rules: #22772

We are also working on extending verification rules:
dotnet/designs#17
dotnet/designs#21

@VSadov VSadov closed this as completed Nov 9, 2017
@jskeet jskeet mentioned this issue Jun 2, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VSadov VSadov

Labels
Area-Compilers Bug Feature - Readonly References Readonly References Language-C#
Projects
None yet
Milestone
15.6
Development

No branches or pull requests
1 participant
@VSadov