As I understand it, it achives lockfree reads by having two caches: One for modifying and one for reading, and atomically swaps them after modifications (and applies the changes to what was previously the read cache).…
Yes you need both compiler barriers for the ordering, as well as memory fences to ensure the global visibility of previous operations in order. It is possible that the mutex implementation he used does no spinning in…
Kinda neat, but why? Who really wants this? It runs a lot slower than a native exe, and waiting for something to load in the browser seems like a silly idea if you could wait for a real program launch.
The const keyword really doesn't mean anything. It is not checked at runtime, so a buffer-overrun could change the const member regardless
That was my point - a lot more people know C
It may or may not be easier to "maintain and extend" a Rust implementation, but it will surely be even easier to find people to do those things if they keep it in C. EDIT: Rephrased the sentence
agreed, it is dangeorus if newbies try to use this
The only times I have ever wanted to freeze an application it was for the purpose of it not hogging CPU time in favor of some interactive program, and had no better way of doing that. On Linux, the Con Kolivas MuQSS CPU…
As I understand it, it achives lockfree reads by having two caches: One for modifying and one for reading, and atomically swaps them after modifications (and applies the changes to what was previously the read cache).…
Yes you need both compiler barriers for the ordering, as well as memory fences to ensure the global visibility of previous operations in order. It is possible that the mutex implementation he used does no spinning in…
Kinda neat, but why? Who really wants this? It runs a lot slower than a native exe, and waiting for something to load in the browser seems like a silly idea if you could wait for a real program launch.
The const keyword really doesn't mean anything. It is not checked at runtime, so a buffer-overrun could change the const member regardless
That was my point - a lot more people know C
It may or may not be easier to "maintain and extend" a Rust implementation, but it will surely be even easier to find people to do those things if they keep it in C. EDIT: Rephrased the sentence
agreed, it is dangeorus if newbies try to use this
The only times I have ever wanted to freeze an application it was for the purpose of it not hogging CPU time in favor of some interactive program, and had no better way of doing that. On Linux, the Con Kolivas MuQSS CPU…