Potential unaligned read

On windows, atty dereferences a potentially unaligned pointer.

In practice however, the pointer won't be unaligned unless a custom global allocator is used.

In particular, the System allocator on windows uses HeapAlloc, which guarantees a large enough alignment.

atty is Unmaintained

A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.

Last release of atty was almost 3 years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• std::io::IsTerminal - Stable since Rust 1.70.0
• is-terminal - Standalone crate supporting Rust older than 1.70.0

See advisory page for additional details.

Hello,

Thank you for sharing your work, I hope you get more time to write fun stuff about your stories with the smol-rs projects.

If you have time, could you show an example of how to use piper for this:

• spawn a thread for reading a file to end (the blocking I/O example in piper docs)
• spawn tasks and pass each "chunk" from the file read to the new tasks, for them to process it

In this case, is there an recommended upper limit on the task creation with easy_parallel?
Is there an internal thread pool that allows re-use of threads, rather than create one per task (of which there may be millions)?