mio-aio 0.9.0

POSIX AIO bindings for mio
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

## [0.9.0] - [2024-05-24]

### Changed

- All types now use I/O Safety.  This means that they take `&BorrowedFd<_>`
  arguments instead of `RawFd` arguments.  This has serious repurcussions for
  consumers who intend to create Futures that have `'static` lifetimes.  It all
  updates the nix dependency to 0.29.0 and updates the MSRV to 1.69.0.
  (#[42](https://github.com/asomers/mio-aio/pull/42))

## [0.8.0] - 2023-08-29

### Changed

- Major rewrite.  The new crate is more efficient.  In particular, it:
  * Does not internally Box the types that must be Pinned.  That is now the
    caller's responsibility.
  * Uses the native `aio_readv` and `aio_writev` functions, instead of faking
    them with `lio_listio`.  This is more efficient, but requires FreeBSD 13.0
    or later.
  (#[29](https://github.com/asomers/mio-aio/pull/29))

- Updated Nix to 0.27.0.  This raises MSRV to 1.65.0.
  (#[38](https://github.com/asomers/mio-aio/pull/38))

### Fixed

- Now sets `EV_ONESHOT`, allowing use in multithreaded contexts where the
  thread that receives notification might not be the thread that calls
  `aio_return`.
  (#[38](https://github.com/asomers/mio-aio/pull/38))

## [0.7.0] - 2022-04-21

### Changed

- Updated Nix to 0.24.  This change raises MSRV from 1.41 to 1.46.

- Updated mio to 0.8.

## [0.6.0] - 2021-09-17

### Changed

- Updated Nix to 0.22.0.  This changes mio-aio's error types, because we
  reexport from Nix.
  (#[21](https://github.com/asomers/mio-aio/pull/21))

- Updated mio to 0.7.

- Added a `tokio` feature flag, which enables extra methods needed by a mio-aio
  consumers that wish to implement Tokio's `AioSource` trait.

## [0.5.0] - 2021-05-31

### Changed

- mio-aio's operations no longer own their buffers.  It is less necessary now
  that async/await is available.  Instead, all mio-aio operations use borrowed
  buffers.

- Most `AioCb` methods now take a mutable receiver rather than an immutable one.

## [0.4.1] - 2019-08-07
### Fixed
- Fixed several dependencies's version specifications.

## [0.4.0] - 2018-11-29
### Added
- Added `BufRef::len`

### Changed
- If an `lio_listio` operation fails asynchronously, the future will now
  include final error status for all failed operations.
- `BufRef::boxed_slice` and `BufRef::boxed_mut_slice` now return `&Borrow` and
  `&BorrowMut` respectively, rather than references to the boxed type.

## [0.3.1] - 2018-07-01
### Fixed
- Fixed Cargo's documentation link

## [0.3.0] - 2018-07-01
### Added
- Support for submitting multiple operations at once with `lio_listio`.

### Changed
- `AioCb` structures can no longer be created from a `Rc<Box<[u8]>>`.  Use a
  `Box<Borrow<[u8]>>` or a `Box<BorrowMut<[u8]>>` instead.

### Fixed

### Removed