-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add Untainted qualifier. #58
Conversation
@@ -62,7 +63,7 @@ | |||
* Constructs a new object. | |||
*/ | |||
@HotSpotIntrinsicCandidate | |||
public Object() {} | |||
public @Untainted Object() {} |
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.
Should you also add tainting to @AnnotatedFor
?
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.
No, all the methods have not been annotated, just this one.
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.
Our current suggestion is to fully annotate files: https://checkerframework.org/manual/#annotating-jdk
j.l.Object isn't very big, so wouldn't it be better to fully annotate it for the Tainting Checker?
The "Whenever you add a file" part no longer makes sense, as all possible files are already contained in the typetools/jdk repository.
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.
We will do that later.
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.
You should at least open an issue to keep track of this.
Merge with typetools/checker-framework#2883.