Julien Portalier

I think IO::Buffered was implemented _before_ we started using libevent.

I agree with both @oprypin and @asterite : as long as we implement target-specific `Int` and `UInt` as the default integer types and we use & recommend those _everywhere_ instead...

Is there really a problem to fix? What's wrong with `src/lib_c` and `LibC` in general? What's the point of introducing yet another module for holding C types when we already...

I think there is a confusion around the extern C world: IMO `LibC` is that whole extern C world (types, syscalls, general ABI), not just a binding to the C...

**I prefer using actual symbols** because it's the actual name and we should always properly name things. Creating fun aliases or renaming struct names, we create a virtual interface, which...

Very nice! What if T responds to `.zero`? Could we use this information to clear the buffer? Granted it wouldn't be a single byte, so it might be more complex...

Indeed, but it's still a "zero" value, so we could set it... but then we can't set the volatile flag to tell LLVM to not optimize (got it). I wonder...

Go merges the counter (i32) and the number of waiters (u32) into a single atomic (u64) which is a neat idea, then uses a semaphore to suspend the goroutines. What...

I'm afraid following on Go won't be possible because their implementation takes advantage of the atomics returning the new value (e.g. add to counter => returns new counter + waiters),...

~~I enabled the waitgroup spec for the interpreter (and disabled the stress test because the interpreter is too slow)... and the interpreter crashed on CI:~~ Errata I didn't push it,...