diff options
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2022-11-28 20:20:35 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-11-28 20:20:35 +0000 |
commit | 89699b1d7f302f6d70f65f650de224ca3afcd62d (patch) | |
tree | 156cdf7be0cfc62a499fc29c600b4e5360ee9074 /.gitignore | |
parent | 33a4d495d99590d17ce4ced675bb6bf4a11d9251 (diff) | |
parent | 006fc6f7975b3a6b64329847b780622aab392109 (diff) | |
download | nix-89699b1d7f302f6d70f65f650de224ca3afcd62d.zip |
Merge #1886
1886: Update use of libc::timespec to prepare for future libc version r=asomers a=wesleywiser
In a future release of the `libc` crate, `libc::timespec` will contain private padding fields on `*-linux-musl` targets and so the struct will no longer be able to be created using the literal initialization syntax.
Update places where `libc::timespec` is created to first zero initialize the value and then update the `tv_sec` and `tv_nsec` fields manually. Many of these places are in `const fn`s so a helper function `zero_init_timespec()` is introduced to help with this as `std::mem::MaybeUninit::zeroed()` is not a `const` function.
Some matches on `libc::timespec` are also updated to include a trailing `..` pattern which works when `libc::timespec` has additional, private fields as well as when it does not (like for
`x86_64-unknown-linux-gnu`).
See also https://github.com/rust-lang/libc/pull/2088
Co-authored-by: Wesley Wiser <wesleywiser@microsoft.com>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions