Oct 12, 2017

Note that one of the co-authors of this paper, Amit, is the author of https://www.tockos.org/

This paper is sort of a successor to https://sing.stanford.edu/site/publications/levy-plos15-tock... , a previous paper on this topic. After publication, Amit solved many of the issues presented there. It was previously discussed on HN https://news.ycombinator.com/item?id=14105884

Some more context https://www.reddit.com/r/rust/comments/655816/ownership_is_t...

Amit left even more context just now on /r/rust: https://www.reddit.com/r/rust/comments/75xwib/the_case_for_w...

Apr 28, 2017

It's the combination of the lambdas and the borrowing system. You have to move all resources into them and then you can't use them from anywhere else.

What I mean is, it's not the closures exactly that are the problem. It's just that closures are one of the times it would be really really convenient if you could have multiple mutable references to something. You end up having to use `Rc<RefCell<>>` as described here:

http://gtk-rs.org/tuto/closures#using-non-gtk-rs-object-into...

This is also mentioned in the Tock PDF: https://sing.stanford.edu/site/publications/levy-plos15-tock... in section 3.2. I'm not really sure how they overcame that in Tock. I guess using RefCell?

Anyway it all seems very awkward.