News for hackers. Stuff that matters.
Re:Baby Steps: Slowly Porting Musl to Rust by astrange on Sunday June 12, 2016 @02:54PM (#11889642)
You can't roll back real side effects like network I/O; that's what it means to be a side effect.

Plus crashing (on some OSes) dumps a lot of useful process state and the current stack, but if a function just returns some error code 50 there's not even a way to find which bits of its internals returned it.

If you separate things by process, you can have your crash-only recovery and keep the rest of the system going.

Re:Baby Steps: Slowly Porting Musl to Rust by nwmcsween on Sunday June 12, 2016 @04:37PM (#11890118)
You can roll back most real side effects like network I/O, console output it just depends on details such as protocol and framebuffer type. You also handle errors at the point of issue, not exceptions.

The issue with separating by process is you have to flush the TLB on context switches.

Re:Baby Steps: Slowly Porting Musl to Rust by dleslie on Sunday June 12, 2016 @04:33PM (#11890109)
This is why "interrupted" and "incomplete" are often valid error states.