Still reading the rustc book, and like, there's so many familiar things going on! Basically feels like a mashup of event emitting like with Choo (5.0) + graph caching like in Bankai/buffer-graph (8.0) + recursion detection like in Barracks (1.0).
-
Show this thread
-
Heh, not quite sure what it means yet, but seeing the parallels is definitely interesting. Something, perhaps unrelated, that I suspect is that JS has had async programming for a long time now which means there's been a lot of development on async / pull-based systems.
1 reply 0 retweets 1 likeShow this thread -
Almost makes me wonder if it would make sense for the compiler itself to be entirely async/await driven? [Big note: I'm not a compiler engineer] It sounds like queries form a graph, performs io, and can/needs to be arbitrarily parallelized — futures sound like a great match??
1 reply 0 retweets 2 likesShow this thread -
Uhh, anyway. Back to vacationing and not tweeting about futures.
1 reply 0 retweets 0 likesShow this thread -
ahahaha, okay yeah last one. So you know how the compiler does incremental compilation? It does this by first loading the previous graph (DAG) into memory, computing the new graph, and then diffs them. Diffing graphs is apparently both a compiler and browser framework thing
1 reply 0 retweets 1 likeShow this thread
Anyway, can highly recommend reading the compiler docs. Very thorough and surprisingly approachable! https://rust-lang.github.io/rustc-guide/query.html …
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.