Fix RLC unsoundness with explicit @MustCallUnknown annotation

[kelloggm]

fixes #6990

[mernst]

Thanks!

[kelloggm]

@mernst I think you should review this again to make sure that the new @MustCall annotations in the Initialization checker are ok.

Also, this change could introduce user-facing behavior in the form of new warnings (as shown by the need to add those annotations). Does that warrant a changelog entry? If so, I don't mind adding one.

[mernst]

@kelloggm CI is not passing. Could you fix that? Then I will review.

[mernst]

@kelloggm Ping.

[Copilot]

Pull Request Overview

This pull request fixes an RLC (Resource Leak Checker) unsoundness issue by adding explicit @MustCallUnknown annotations to prevent incorrect behavior when handling owning parameters with unknown must-call obligations.

• Adds proper error detection for @Owning parameters with @MustCallUnknown annotations
• Improves must-call type resolution by using hierarchy-aware annotation lookup
• Adds type annotations to initialization classes to ensure proper type checking

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
DropOwning.java	New test case demonstrating the fix for issue #6990 with expected error
CrashForTempVar.java	Adds suppression annotation to focus testing on crash detection
MustCallConsistencyAnalyzer.java	Updates annotation lookup logic and fixes typo in comment
InitializationTransfer.java	Adds @MustCall type annotations to class declaration
InitializationStore.java	Adds @MustCall type annotations and improves class documentation