Jan Behrens

Related: [Rust `std` doc issue #91004](https://github.com/rust-lang/rust/issues/91004).

Unless access becomes restricted to privileged users (root) only, I would propose to make `snapdir=disabled` the (safe) default, because I see the current behavior as a security vulnerability (as pointed...

From [Issue #104814 on Rust](https://github.com/rust-lang/rust/issues/104814): > […] it should be clarified whether the difference between the Rust documentation and the C++20 reference exists intentionally, i.e. is Rust deliberately giving less...

See also [this thread on URLO](https://users.rust-lang.org/t/out-of-bound-compile-error-with-len-function-call/77342).

> But where does a received CRC end up? Regarding `NP_HANDLE_CRC`, the CRC seems to simply end up in the response (when authorizing, I get four instead of two bytes),...

I think I ran into a similar or the same issue that boiled down to this: ```koka fun main() var a := () fun inner() // commenting out either(!) of...

Some simple example of how I see it works currently (Koka 3.2.2, 39b4bec7327dbbcb2f83ce7aca5fe061931a4dc3): ```koka pub named effect fuse fun trigger() : () fun was-triggered() : bool pub fun new-fuse() :...

Regarding to what I wrote above, > I'm not sure if that's really intended. It basically means that values in Koka may have "inner mutability". basically it means we can...

> But I don't think that [effects / effect types] are intended to reflect _everything_ that might happen, or prevent all bad behaviors. I guess that's true for every type...

> When we create a new ref, we unwind to the `heap` effect, insert the handler for the new ref, and then rewind the stack. All ref handlers and their...