Marc Knaup

FYI `capitalize` as it is implemented today uses titlecase. Uppercase only as a fallback.

There are three transformations for characters: "titlecase", "uppercase" and "lowercase". So it makes sense to offer three transformation methods: - `titlecaseFirst()` transforms the first character to titlecase. There is no...

There are plenty of examples for non-"ed" names, esp. around Strings, Collections, Sequences and Flows. So it's kinda consistent. - `.capitalize()` - `.drop…()` - `.encodeTo…()` - `.replace…()` - `.slice()` -...

`as…` doesn't refer to mutability but rather that it wraps an existing value and uses it internally even after the function has returned. That's relevant for example if `Iterable` can...

As far as I understand this KEEP is mostly about duration and timing related to measurement, timeouts etc. and not for real-world date/time application. I suggest to be careful with...

Great and thorough proposal with quite a lot of history 🙌 ### `context` Syntax I thought exactly the same as @altavir. Here it's especially bad: `var g: context(Context) Receiver.(Param) ->...

@mcpiroman it's [already mentioned](https://github.com/Kotlin/KEEP/blob/context-receivers/proposals/context-receivers.md#contextual-classes-and-contextual-constructors) as a potential future extension.

Another naming-related issue came to mind: - We have `context` on the consuming side. - We have `with` on the providing side. - We have `withContext` in `kotlinx-coroutines`. I already...

@edrd-f > @altavir @fluidsonic - about the suggested `` syntax, the problem is that in `context`, `Comparable` is a literal type while `T` is a generic type, so the semantic...

How will this affect code coloring due to `@DslMarker`? Let's take my current Kotlin/JS project with plenty of React & CSS DSL coloring for example.    As soon...