We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider the code given below.
@Unique class Data { Object check(Data p) { return p; } // No error Object check2(@Unique Data p) { return p; } // No error }
When the code is compiled by the Aliasing Checker, it doesn't raise any error even when the object is explicitly annotated.
Shouldn't it ideally raise an error in the return p line, since Data p is @Unique and is now leaked?
return p
Data p
@Unique
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider the code given below.
When the code is compiled by the Aliasing Checker, it doesn't raise any error even when the object is explicitly annotated.
Shouldn't it ideally raise an error in the
return p
line, sinceData p
is@Unique
and is now leaked?The text was updated successfully, but these errors were encountered: