You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a planning issue for a 1.0 release, similar to the one for the 0.38 release. Hopefully we won't need a semver bump for a good long while, but when we do, here's the list of changes we can make:
Remove the deprecated mount functions in the fs module (details)
Make the underlying type of rustix::fs::Access consistent between linux_raw and libc backends (Port 1.0-staging to main #1152)
The udata argument to rustix::event::kqueue::Event::new should be a pointer instead of an isize in order to better preserve provenance. (Make APIs preserve strict provenance. #1270)
The stx_attributes_mask field of Statx with flags like libc::STATX_ATTR_MOUNT_ROOT should ideally be a bitflags, which requires making Statx a custom type (which should match layout with libc::statx). (Reorganize Stat, Statx, and SockaddrStorage #1282)
Rename get_* functions (eg. sockopts) to remove the get_ prefix, which is more idiomatic Rust?
move rustix::thread sleep functions into a new rustix::sleep module, because they're usable from single-threaded programs too
Move Dir into its own crate, and have rustix export getdents directly?
Split open and openat into separate functions for "create" which needs a mode vs. "open existing" which doesn't need a mode?
Make RecvAncillaryBuffer::drain always remove all messages, even if the iterator isn't exhausted. With that, we can remove the read_and_length in AncillaryDrain.
Replace rustix::cstr! with something like rustix::nativestr! so that users don't hard code "native strings are C strings" in their code?
rename Arg::as_str to avoid "a method with this name may be added to the standard library in the future" warnings
rustix::process::waitpid has no way to wait for specific process groups (Pid now requires non-negative values). waitpgid has been added as a temporary workaround.
I've now published rustix 1.0.0-prerelease.1. Please test out the prerelease, and please comment on if there are any problems or if there are any changes we should consider before releasing 1.0.
I've documented all the API changes I'm aware of here; please let me know if anything there is unclear or if there's something not covered.
Thanks for the reports! I've now done more testing too, and fixed a few issues that came up. I think everything is ready for a 1.0.0 release. I'm thinking of doing the release two days from now, unless any problems surface.
Here's a planning issue for a 1.0 release, similar to the one for the 0.38 release. Hopefully we won't need a semver bump for a good long while, but when we do, here's the list of changes we can make:
fsmodule (details)rustix::fs::Accessconsistent between linux_raw and libc backends (Port 1.0-staging to main #1152)mount_recursive_bindtomount_bind_recursive? Factor out a new top-levelmountmodule. #763 (comment) (Renamemount_recursive_bindtomount_bind_recursive. #1273)SeekFrom::HoleandSeekFrom::Data's field fromi64tou64. (Make the offsets forSeekFrom'sHoleandDataunsigned. #1266)Shutdown::ReadWritetoShutdown::Bothto align with std (RenameShutdown::ReadWritetoShutdown::Both. #1264)features = ["extra_traits"]from the libc dependency (Remove the "libc-extra-traits" feature. #1168)sched_yieldand othersched_*functions fromprocesstothread, since they apply to threads rather than processes on Linux etc. (Movesched_*andmembarrier_*intorustix::thread. #1265)stx_mtimeand similar members ofStatxshould bei64, because Unix timestamps can be negative.futex's first argument should beAtomicget_from sockopt getters, following Rust convention. Consider removingget_in other things too. (Rename sockopts getters to remove the "get_". #1269)udataargument torustix::event::kqueue::Event::newshould be a pointer instead of anisizein order to better preserve provenance. (Make APIs preserve strict provenance. #1270)stx_attributes_maskfield ofStatxwith flags likelibc::STATX_ATTR_MOUNT_ROOTshould ideally be a bitflags, which requires makingStatxa custom type (which should match layout withlibc::statx). (Reorganize Stat, Statx, and SockaddrStorage #1282)get_*functions (eg. sockopts) to remove theget_prefix, which is more idiomatic Rust?MountPropagationFlags::SLAVE(Rename a flag inMountPropagationFlags. #1169)WaitidOptions,WaitidStatus, and/orWaitIdto make the capitalization ofIdconsistent (RenameWaidid*toWaidId*, for consistency withWaitId. #1267)inotify_prefixes from things in thefs::inotifymodule.shm_andShmprefixes from things in theshmmodule.recvinto an uninitialized buffer with theTRUNCflag set (see Fixrecv_uninitto handle theTRUNCflag. #1159) (Report the number of received bytes inrecv_uninitandrecvfrom_uninit. #1278)io_uring_register_files_skipfrom aconst fnto a constant. (Replace theio_uring_register_files_skipfunction with a constant. #1268)Deferring for now:
Dirinto its own crate, and have rustix exportgetdentsdirectly?openandopenatinto separate functions for "create" which needs a mode vs. "open existing" which doesn't need a mode?RecvAncillaryBuffer::drainalways remove all messages, even if the iterator isn't exhausted. With that, we can remove theread_and_lengthinAncillaryDrain.rustix::cstr!with something likerustix::nativestr!so that users don't hard code "native strings are C strings" in their code?Arg::as_strto avoid "a method with this name may be added to the standard library in the future" warningsrustix::process::waitpidhas no way to wait for specific process groups (Pidnow requires non-negative values).waitpgidhas been added as a temporary workaround.Don't do these:
set_ip_add_membership/get_ip_add_membershipshould takeaddressandifindexarguments and*_with_ifindexshould be removed.ClockId::Uptimeon FreeBSD toBoottime, since it's an alias