IssueTracker

It seems that there are some cases where @Experimental doesn't correctly warn on experimental api usage when called from Java.

Here's a sample project:
https://drive.google.com/file/d/18cYt2O4MiTHmHet_ng-jquKpX2-q2lru/view?usp=sharing

In the sample usages of experimental APIs in ExperimentalUsage class
    public void main() {
        // Should raise a lint warning?
        new ExperimentalApi().experimentalFn();

        // This correctly raises lint error.
        //noinspection KotlinInternalInJava
        BenchmarkState.Companion.reportData(null, null, 0, new ArrayList<Long>(), 0, 0, 0);

        // Should raise a lint warning?
        BenchmarkState.reportData(null, null, 0, new ArrayList<Long>(), 0, 0, 0);

        // Should raise a lint warning?
        new ExperimentalApi().experimentalJavaFn();
    }

Only 1 / 4 of these  correctly warn the user of experimental api usage