https://kotlinlang.org logo
#compose
Title
# compose
r

romainguy

06/14/2019, 6:51 PM
@miha-x64 Why do you think that? I'm curious to hear what we could improve
m

miha-x64

06/14/2019, 8:11 PM
Remove compiler plugin and all annotations, make everything (including receiver) explicit. As a bonus it will become Java-compatible. https://twitter.com/miha_x64/status/1137677887656603649
👎 4
r

romainguy

06/14/2019, 8:31 PM
Thanks for the reply. That would be a big departure and not where we want to go unfortunately.
k

kioba

06/15/2019, 7:47 AM
I had the same concerns regarding compose. I had to understand more about the compiler plugin approach and I can see now that there is benefits in it. I feel there is not enough resource about this concept yet and for that reason feels magic and dangerous for developers. do you think just itself the
"returns nothing, has side-effect(s)"
would be also a too big change? I am just curious, and would like to understand more about the decisions around compose
g

gildor

06/15/2019, 12:22 PM
@kioba have you checked this blog post? http://intelligiblebabble.com/compose-from-first-principles/
👍 3
m

miha-x64

06/15/2019, 3:35 PM
feels magic and dangerous for developers.
Yep, patching a data tree is a trivial task which should have as simple solution as possible. And it's not about UI, it's useful for any generic data.
6 Views