Golang and Rustlang Memory Safety https://insanitybit.github.io/2016/12/28/golang-and-rustlang-memory-safety …
Not apples-to-apples. I suspect it will become common to disable any such features that have runtime costs in Rust programs.
-
-
Especially when we've eliminated more `unsafe` from libstd/libcore, eliminated libc dependency, and have more pure Rust libs.
-
personally, I’m fed up with writing libc-isms in Rust. We could have a much nicer API over syscalls
-
Which specific APIs would be most improved?
-
mostly filesystem related functions. The network part has good libraries, and nix works well for process interaction
-
but dealing with filesystem functions requires swinging CStrings around again and again
-
I think that Windows often is the limiting factor in those situations, for most APIs that attempts to be cross-platform.
End of conversation
New conversation -
-
-
ASLR is free. Note that it's only base randomization. Rust already uses jemalloc which is the opposite of hardened.
-
ASLR defeats prelinking so it can't be free. The use of jemalloc by default is (hopefully) changing soon.
-
Naive prelinking is similarly incompatible with proper code signing. Almost everyone stopped using it anyway.
-
Prelinking has time and storage usage costs too and base randomization screws it up unless you are disabling it all.
End of conversation
New conversation -
-
-
There is no perf cost on modern platforms(x86_64). Disabling is a bad idea regardless.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.