Manu Sridharan

Did some investigation on this one, and it looks like at least one issue is we do not have handling of postconditions when they impact temporary variables. We have special...

Thanks for digging into this @kelloggm. One question: > converts and viewpoint adapts the argument to the postcondition annotation to get a JavaExpression. For example, this converts "#1" to a...

I guess what I don't understand from suggestion (1) is why it would take a `JavaExpression` as an input? Shouldn't it take the same inputs as the viewpoint adaptation code,...

I did some further investigation and understand this one better now; see #6375. At this point I don't think it's worthwhile to fix this case, given the implementation effort and...

I am also amazed how far you got @Calvin-L! Unfortunately I don't really see a way to get around 2 with the current RLC either. What we really need is...

I would support allowing for suppressing warnings at the `static` field definition, and a flag if we find that there is a common pain point of having many `static @Owning`...

@smillst does this look like #979 to you?

@janrieke I'd also be interested to hear about your experience running the Called Methods Checker on Lombok builder code without de-lomboking. If you run into issues please let us know!

Very interesting @Calvin-L! It'd be cool if in fact CF and Lombok could be run together. I wonder if the interaction flakiness would be reduced further if at some point...

@jacek-lewandowski we are actively brainstorming on how to add support for this. If you could link an example using an array of resources showing how they get closed it could...