Damn you know what I would kill for? A visual drawing of lifetimes. Like I have somewhat of an intuitive sense after all these years but I don't really get it and everyone keeps using words, give me diagrams damn it. "'a lives as long as" no stop draw it for me pls i beg of u
-
-
-
Replying to @grooveplex
that would be sick, but things like recursion, loops, and closures would really mess with that :(
1 reply 0 retweets 1 like -
Replying to @mgattozzi
I think the biggest problem would be a confusing UI. The lifetime information has to be stored *somewhere* in rustc.
1 reply 0 retweets 1 like -
Replying to @grooveplex
right but it's not there forever after a certain point it gets thrown out. not saying I don't want it, just the work to get it right is a lot
1 reply 0 retweets 1 like -
Replying to @mgattozzi @grooveplex
My hope is that Chalk will eventually be used for reasoning about lifetimes, at which time you could build arbitrary tools and visualizations on top of it.
1 reply 0 retweets 2 likes -
-
Replying to @grooveplex @peidran
It's a trait solver that's been worked on separately for awhile (kind of like prolog) that when/if it's integrated to the compiler would provide a lot of benefits around things like trait resolution and solving for lifetimes
1 reply 0 retweets 3 likes -
Benjamin Fry 🦀 👾 ⚙️ Retweeted rust-analyzer
Looks like the rust-analyzer just got Chalk integrated, maybe a future feature for this will come? https://twitter.com/rust_analyzer/status/1252166644262109186?s=21 …https://twitter.com/rust_analyzer/status/1252166644262109186 …
Benjamin Fry 🦀 👾 ⚙️ added,
1 reply 0 retweets 1 like
To clarify, chalk has been integrated with rust-analyzer for a long time. What happened in this release is that we've switched to a different implementation of solver *inside* chalk. The original impl wasn't good enough for some common cases.
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.
