-
Notifications
You must be signed in to change notification settings - Fork 10
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
New features and improvements #216
base: master
Are you sure you want to change the base?
Conversation
… flag is f*ing hard
…or crate and codelenses only updating after reloading a file or editing it.
verifying different files or crates, not just the info of the most recent one is stored.
…lecting information but not verifying
Not yet actually depending on the verification's result.
…with displaying it
…s. However the textual decorators just stack in subsequent verifications so they will have to be removed at some point
… crash message upon kill.
Can you try adding the following configuration to the "rules" section of
What's important to me is that there are no linting errors. Linting errors that are too restrictive should be downgraded to warnings in the linter's configuration if they still provide some value, or disabled at all if they are too noisy. |
@Aurel300 this means that we should publish a >=0.3.0 Prusti release before merging this PR. |
Yes, I know, that's what viperproject/prusti-dev#1334 will do. |
Practical Work project by @jthomme1 and me, supervised by @Aurel300.
The new features include:
Additionally, @jthomme1 did a rather extensive refactoring of the diagnostics and verification parts.
To use these new features, prusti needs to be at least at version 0.3.0.