Dan Gohman

Yes, `raise` and `tgkill` can go in `rustix::thread`, and be implemented in the libc backend as well. `tgkill` is `cfg(linux_kernel)`, and on musl it looks like it'll need to go...

@6A Do you have any thoughts here?

I think it makes sense to include some form of pthread.h in the include directories for all targets. At one time I had the idea to exclude it so that...

Additional history: This issue also [surfaced](https://esdiscuss.org/topic/es6-accuracy-of-special-functions) in 2014. TC39 discussed it in person [here](https://github.com/tc39/notes/blob/main/meetings/2014-07/jul-31.md#precision-of-math-trig-functions) and [here](https://github.com/tc39/notes/blob/main/meetings/2015-05/may-27.md#test262-update-bt-presenting). At the time, there seemed to be general agreement that math functions should be...

I've now released cap-std 2.0.2, which I expect fixes this.

> I also imagine various FUSE filesystems (eg, s3fs) do the bulk of their work only when close is called. FUSE for its part [documents](http://libfuse.github.io/doxygen/structfuse__operations.html#ad4ec9c309072a92dd82ddb20efa4ab14) that filesystems should avoid doing...

> @the8472 and @sunfishcode I would like to understand - > > 1. Are you folks opposed to having an explicit close() that returns an error? I myself am. >...

I've been experimenting with the `Buffer` trait in a standalone [buffer-trait](https://docs.rs/buffer-trait/latest/buffer_trait/) crate, which has an unsealed trait and a more complete API. Crates like `bytes` probably won't ever want a...

Closing, as the [buffer-trait](https://docs.rs/buffer-trait/latest/buffer_trait/) crate is the path forward here.

If you want to write a wrapper around rustix, I imagined you could use `rustix::buffer::Buffer` and just forward the buffers to rustix's functions. If you want to write your own...