Vsevolod Tolstopyatov

Could you please provide a simple reproducing project? The fix is slightly more complicated than that because this check is necessary to filter out root projects without sources

No progress. I'm ready to accept a contribution (as long as it's accompanied with a corresponding test) or a reproducing project to help me reproduce and fix the issue

@drewhamilton it's better to create a separate issue

That's a nice catch! It's not a public API, but it is, technically, a public ABI similar to how `inline` functions are -- it can be inspected/called via reflection without...

Thinking about it a bit more, it's definitely not part of ABI, because reflection is not part of it. And `inline` functions are because they can be invoked **directly** from...

Binary-compatibility-validator is intended to be used only with JVM targets. There is no public notion of "binary compatibility" in either JS or K/N, so they are not supported

Good point, I will update the readme

I wonder how this translates to Java interop stability. But I guess if it's annotated and the documentation is straightforward, it shouldn't surprise anyone

Hi, thanks for the report. Unfortunately, there are no plans to change that in the nearest future due to the lack if time, but I'll try to get back to...

The separate type is useful for potential future additions on a standard library level instead of a language one. E.g. we can potentially extend `EnumEntries` to have such members as...