You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO this is going to be a challenging one. We made a jokey decision early on to not say the words "lvalue" and "rvalue" on the podcast, as a symbol for going wayyy off into the weeds of PL/compiler theory land.
In particular, this RFC worries me because in the text and comments I see:
Acronyms I don't understand like VLA
Concepts I don't understand like alloca
Greek symbols
Assembly
So perhaps this RFC would be especially good to explain because it reads pretty impenetrably to me, but the challenge imo is bringing this down to the practical and explaining how this will affect how people write Rust and how Rust code works.
I just wanted to note about the challenge level here :)
/cc @aturon are you up for the challenge??? Or is there someone you'd have in mind that would be especially good for this one?
The text was updated successfully, but these errors were encountered:
rust-lang/rfcs#1909
summary comment: rust-lang/rfcs#1909 (comment)
IMO this is going to be a challenging one. We made a jokey decision early on to not say the words "lvalue" and "rvalue" on the podcast, as a symbol for going wayyy off into the weeds of PL/compiler theory land.
In particular, this RFC worries me because in the text and comments I see:
So perhaps this RFC would be especially good to explain because it reads pretty impenetrably to me, but the challenge imo is bringing this down to the practical and explaining how this will affect how people write Rust and how Rust code works.
I just wanted to note about the challenge level here :)
/cc @aturon are you up for the challenge??? Or is there someone you'd have in mind that would be especially good for this one?
The text was updated successfully, but these errors were encountered: