binary-compatibility-validator
binary-compatibility-validator copied to clipboard
Do not report public synthetic constructors of sealed classes as public API
It is mostly a compiler omission (KT-26436, KT-25112), but creates a false sense that such constructors are part of public ABI
I came here to file an issue that protected functions in sealed classes should not be reported, and found this similar issue. Do you want to consider that as part of this issue or should I file a separate issue?
@drewhamilton it's better to create a separate issue