* AsyncWrite/Read/Seek
* clean up
* use only one field to store the future
This struct should not be shared across threads because simultaneous
operations
like reading, writing, or seeking could lead to data races or
inconsistent state, because the cursor moves.
Only one operation will ever run at a time, which allows us to safely
store
different types of pending operations (read, write, or seek) in the same
field.
* consume self without mut when closing
* clippy
* Add inner_file safety tests
* more tests
---------
Co-authored-by: Jackson Coxson <jkcoxson@gmail.com>
