If this is going to be useful in Rust, it needs to be borrow check compatible, since we borrow check MIR. The strict SSA is already a potential problem. I’m open to being convinced otherwise, but right now I’m skeptical.https://twitter.com/migueldeicaza/status/1097846352183214081 …
-
-
Ah, yeah we model "inout" (aka &mut) as a memory location too. That's always an escape hatch in LLVM-style SSA, put the stuff that doesn't fit the model in memory

-
SSA with additional formation rules to control ownership transfer OTOH feels pretty natural for modeling shared borrowing and moving
- 6 more replies
New conversation -
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.