Martin Kellogg

I've pushed a similar example that uses the Nullness Checker to demonstrate the unsoundness to the same branch I mentioned in my previous comment (you should be able to see...

> Is there a way to take over the ownership each item of a vararg / array / collection? Unfortunately, no. This is a known limitation of the RLC; see...

> Maybe there could be an annotation which would mark a collection immutable? > One complication is aliasing (mutations through aliases). One option would be to trust rather than check...

Hi @jacek-lewandowski, I took a look at this example. I don't think it indicates a bug in the checker per se: rather, I think the issue here is that the...

> Do the confusing error messages have the same root cause as https://github.com/typetools/checker-framework/issues/4947? Yes. > Reading the code, however, it looks like one or the other is invoked. So I'm...

> I must say I'm confused - the documentation says explicitly that it can be OR: Sorry that this documentation is a bit confusing. Let me explain further (and if...

These warnings are a consequence of imprecision in the analysis when analyzing method references. They can safely be suppressed. It would be nice if the RLC didn't warn in these...

I'd prefer to leave this issue open, because these warnings are false positives and it would be great to fix them if we can figure out an easy way to...

That said, this is probably wontfix

This problem also occurs for interfaces, which might present another challenge. Consider the following (which I've now checked into the same test case on the same branch): ``` interface MyInterface...