-
Notifications
You must be signed in to change notification settings - Fork 112
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
No cache #964
No cache #964
Conversation
304caae
to
7699a65
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like a justification on the removal of contracts, since I don't understand this part.
|
||
public void Insert(Implementation impl, ImplementationRunResult result) | ||
{ | ||
Contract.Requires(result != null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Contract.Requires(result != null); | |
Contract.Requires(impl != null); | |
Contract.Requires(result != null); |
This contract was left out during refactoring. Or did you intend to remove both contracts?
The function Lookup, RemoveMatchingKeys and VerificationPriority below also had a contract removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The presence of the contract creates a warning slightly further down in this method, because it implies impl
can be null
and this file uses #nullable enable
. I had to remove the check because the warning makes the build fail.
The end-state we want is that all files use #nullable enable
and there are no more Contract
based non-null assertions.
Changes
EmptyVerificationResultCache
Testing