Any pointers to a good treatment on why one can’t build an efficient library usable from C in a language that prevents raw memory access?
Apr 9, 2014 · 9:00 PM UTC
5
2
3
@stilkov you retweeted this post which shows how this already failed if the app doesn't use the "library" properly: article.gmane.org/gmane.os.o…
1
@alexkli But that’s a different thing. Clearly there’s no protection against the users using a lib wrongly
1
@stilkov "prevent raw access" or "makes raw access safe", For the later I seem to recall that Microsoft Research had lang for device driver
@raganwald @stilkov this was an attempt to optimize around malloc; it’s even more tempting to optimize around GC
@stilkov I wouldn't know of any. BTW, building runtimeless shared libs following the C-ABI is a supported use-case for Rust.
1