ilya-g

> If it's in separate modules a project can just say "we don't use that library" and stay consistent. I believe this can be achieved without such radical measure as...

@quicknir, Could you tell from your experience working with `std::chrono` what real world use cases does a time point being representable as a duration since epoch enable?

Following the feedback from Google's GoodTime team, we've decided to rename `Clock` interface to `TimeSource`, see PR #205. The original plan was that `WallClock` class from date/time library could implement...

One of concerns often voiced in the feedback regarding the Duration type is that the extension properties on numeric types used to construct a Duration could pollute the completion of...

If this proposal is implemented, we're going to relax some stdlib function signatures by removing `T : Any` constraint from them and using `T!!` (or `T & Any`) type instead....

With the planned introduction of `rangeUntil` operator, we're proposing an alternative approach for representing open-ended ranges. See details in the KEEP #314.

@juangamnik Could you clarify in the proposal, what scope is used for resolving method calls for reified types in inlined function: either it's the scope of inline function declaration, or...

@juangamnik > I misunderstood you, but do you want me to describe the current situation in Kotlin or the intended situation (of the proposal)? As the proposal is going to...

> So this leaves call-site scope for the moment, right. And you would like me to elaborate on this and the possible conflict situations that may arise and how to...

> Should I add this example to the proposal? definitely, it would be valuable. > The compiler will inline this and should then throw the error, that the inline function...