Dan Gohman

CC @haraldh. It's possible this is related to how WASI programs discover the preopened sockets. Would it work to do the `self.compute_preopen_dirs()` before the `self.compute_preopen_sockets()`, so that the directories have...

WASI is in the process of moving to interface types and Typed Main, at which point I expect we'll completely overhaul the way file descriptors are passed into programs. The...

Just as a heads up, x87 floating point does not produce the same results as other platforms including SSE in various cases, and the spec testsuite has tests which care...

Using `LD_PRELOAD` to intercept syscalls is complicated by the fact that glibc's own calls to syscall wrappers often use internal symbols that can't be replaced with `LD_PRELOAD`, so not all...

An alternative I don't see mentioned yet is to use a `let` to split the multi-line expressions into its own line, like this: ```rust // prefix match, but using `let`...

The main concern about adding socket addresses to core seems to be: > If the socketaddr types aren't identical across platforms, I don't think we want them in core. I...

I'm working on a project which opens up another option: [rsix](https://crates.io/crates/rsix). It's similar to syscalls-rs mentioned above in that it can use native-linux syscalls, but it's structured to have configurable...

Here's a more specific testcase: ```sh $ echo -e '\x90' > test.txt $ target/debug/examples/parselog < test.txt [execute] 0a $ ``` The 0x90 byte is silently dropped with no `execute` or...

I don't actually want to interpret C1 controls in my use case; I want to replace all non-UTF-8 bytes into replacement characters. Right now, vte doesn't support that, either for...

> You could just handle C1 escapes in your application by printing the missing glyph symbol, would that be reasonable? As far as I can tell, all that would be...