or rather, the state variable is bound-on-acquisition, and its assumed that functions you call will be re-run as needed if they receive some sub-field of that value
-
-
Replying to @__anp__ @raphlinus and
There's a high bar to reach for compiler level plugin. It was/is a gamble, but makes sense for us I think. Once you have it, lots of potential to improve ergonomics though.
1 reply 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
I'm not certain that the implicit observation of
@Model was the right call or not, but it does have a lot of advantages. That said, yeah - might not make sense in the context of rust. Swift UI made similar judgement calls i suppose.4 replies 0 retweets 1 like -
Replying to @intelligibabble @jckarter and
Rust makes things interesting in lots of ways. Thing is, we can evolve the language if need be, but I think we need a *really* good story of what that should be and why we need it. I personally don't feel like I understand the domain well enough yet. JC is inspiration here.
2 replies 0 retweets 1 like -
Replying to @raphlinus @jckarter and
Yeah. I am trying to look at JC through the lens of "what is specific to Android + UI, and what can be more general as a language feature". What is exciting is that as time has gone on we have been able to simplify what
@Composable actually means to us more and more1 reply 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
The best parallel IMO is with async/await. Several languages have now adopted this type of feature. I *think* as we iterate on things, it will become more clear what a composable function is / what it's useful for, and we can formalize it.
1 reply 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
From my perspective, positional memoization is at the heart of it all. I was really interested in skip (the language) when it came out because of this, but the approaches are pretty different
1 reply 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
having a global memoization cache is problematic, i think. There are several things that the "positional" type of memoization solves, and i think it can be thought of as being more broadly useful.
1 reply 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
once we get a bit more stable, i have a couple of blog posts i'd like to write to maybe inspire people in terms of what else could be built on top of compose (some not UI related at all). and i'm hopeful that people find things that i haven't even thought of yet!
2 replies 0 retweets 1 like -
Replying to @intelligibabble @raphlinus and
a real "life goal" type victory for me would be to see some other language (ie, not kotlin) actually implement something like
@Composable because it is seen as something more broadly useful1 reply 0 retweets 1 like
I already see the strong parallels with async/await. I certainly agree this is very interesting, and much worth exploring. Rust was able to experiment with an await! macro for a while, limitations compared with the real thing but still interesting.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.