comex

> I've expressed a concern about the proliferation of different wrappers with nuanced differences in which invariants they relax. I think the difference between this description and yours is a...

> The other thing is that if the compiler handled it then we could make no_mangle a safe attribute, but we're just not doing that. That’s quite impossible if you’re...

Which is why I think `let` should become an actual boolean expression, albeit with special rules around scoping. That solves the “random recycling” problem and also enables `if !let`.

(and while this is admittedly both rude and off topic :\\, after checking your recent posts, is there *anything* you’re not against?)

@andrewcsmith `some_slice[2]` is already `i32` - you need `&some_slice[2]` for `&i32`. The indexing operator carries an implicit dereference. (`some_slice` is also not a slice...)

Yep. I’m not a Windows expert, but to quote [MSDN](https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminatethread) on the API that would be used to kill a thread: > **TerminateThread** is a dangerous function that should only...

Any update on this? :) I'm a user of enet who thinks IPv6 support would be quite nice to have.

Thanks for the reply. From an API perspective, my thought was to do something like - add `ENetAddress2`, which has a family field (and reserves 128 bytes of space or...

If anyone reading this is impatient like me, I found a hacky alternative way to map keys. This only works with AppleEmbeddedKeyboard, which is most/all of Apple's own keyboards (run...

I think that ideally there should be a way to compile the invariants to regular code and check them as runtime asserts, whether with quickcheck or some new crate. Thus,...