Eduardo Fonseca

Hey @akuleshov7, nice work! I checked some parts of the code and have a suggestion to improve the public API. I agree with @Olivki that top-level `serialize` and `deserialize` functions...

@akuleshov7 Looks great!

Design doc: https://hackmd.io/ntPqhK31Qw64OvwFQN4YfA

What about `uppercaseFirst` and `lowercaseFirst` instead of `capitalizeFirst` and `decapitalizeFirst`? Looks more intuitive since capitalization is related to the whole string, so `(de)capitalizeFirst` sounds strange.

Problem is that it's only one letter from the original `(de)capitalize()` functions, making it easy to use the wrong one, especially with IDE autocomplete.

Were union types considered as a possible solution? i.e.: ```kotlin open class MyTask { var input: Property = Property() set(value: Property | File | Path) { field = when (value)...

> > Were union types considered as a possible solution? > > They were considered. Unfortunately, this is a really big feature and as I understand it's still far away....

Some questions: 1. Will the assignment overload work for literals? ```kotlin operator fun Any?.assign(other: Any?) {} fun main() { "x" = 1 // Will this compile? } ``` 2. Will...

> With that in mind, it makes no sense to implement a custom assign operator except if you have an actual specialized type that operator overload makes sense for. So...

That's awesome. Thanks @asodja, Gradle team and Kotlin team for listening to the community. :heart: