Jacob Lifshay

> > One idea I like from that thread is to make the guest responsible for creating a temp folder and adding that to its internal preopens list. This turns...

`fmt::Write` is problematic because it can't properly keep error information by itself, since the error type is a ZST. I think it would be better to have a method like...

I think it would be useful to prevent seeking to before the initial position, so `Take` essentially just lets you see a defined range of the wrapped file-like thing.

there's some minor cleanup that someone with permissions (@tgross35?) needs to do (https://github.com/rust-lang/rust/issues/97227#issuecomment-2892560898 and https://github.com/rust-lang/rust/pull/138023#issuecomment-2892555305), but yeah afaik you can close this issue.

if we want `[MY_NAMED_CONST; N]` syntax to work with things other than arrays, maybe we need a built-in macro `is_expr_copyable!` that is true if the passed-in expression is a `const`...

> `continue ` could be guaranteed to jump directly to the right arm if `expr` is const promotable so then if I were to try to use this to write...

what if you had to write `static continue 'a expr` to get the jump directly to match arm semantics (and requires being able to figure out which match arm to...

> I never like these proposals because labels feel like a last-resort kind of feature in rust but can you express computed goto using `loop match` (e.g. with an enum...

> Didn't a certain @programmerjake demonstrate above how to do this using a macro? not really, because the macro I wrote would produce N separate jump tables for the N...

I think we should try to match `repr(system)` to `extern "system" fn` -- we already have the latter, why not the former? as for matching the C ABI, I think...