Wow, this is extremely relevant to my current work (porting from Go to Rust). Adding on to the paper, some other issues are: - Modeling concurrency across boun

Wow, this is extremely relevant to my current work (porting from Go to Rust). Adding on to the paper, some other issues are: - Modeling concurrency across boundaries, like if you're p using goroutines but also tokio, how the heck does that work? - Persisting data across FFI, like if you have some Go code that calls Rust, and you want the Rust code to persist stuff in memory, that gets tricky fast. - Assumptions around strings. Go will give you a bag o' bytes and say "it's a string, trust me!" while Rust expects UTF-8. We definitely ran into some of these issues, like remembering who should deallocate which memory.