Vsevolod Tolstopyatov

1) >Contracts primarily consider the behavior of methods rather than the properties of values. **Properties of values should be handled by the type system rather than contracts.** Could you please...

>Sorry, I think you mean "non final" functions? No, I meant final functions. Inheritance is not designed, but contracts are still not allowed in final member functions for some reason....

The request itself is quite reasonable, though unfortunately, it's out of my scope right now. I'm ready to accept a high-quality PR (with tests and docs) in a timely manner...

Good point with covariant return types! Though it seems to be more complicated than that. Consider the following scenario: I extend **3rd-party** class `A` (that is e.g. unstable), override all...

Note to self: ``` class ConstructorMarker constructor(unused: String = "") ``` and ``` class ConstructorMarker private constructor(unused: String, i: Int) { class Builder { fun build() = ConstructorMarker("", 42) }...

We decided this is a compiler issue: https://youtrack.jetbrains.com/issue/KT-51073 Alas there is not much we can do on BCV side to address it

Good point. I'm not sure how hard it would be to add it and if there are any caveats that may prevent us from implementing it though. I'm ready to...

❤️

Hi folks and sorry for our (missing) PR handling policy! We've discussed it internally and would like to discuss an alternative proposal. We do acknowledge the need of `measureTimeMillis` and...

>Maybe DeprecationLevel.NOTE? Or INFORMATIVE? Love the suggestion. I'll try to write a proper YT proposal (aka pre-KEEP) around next week and will definitely use these as viable options