-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0 release planning #753
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
As discussed [here], use generic parameters instead of impl trait argumentst. [here]: #753 (comment)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
As discussed [here], use generic parameters instead of impl trait argumentst. [here]: #753 (comment)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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. |
Just did the upgrade in Ringboard and it went pretty smoothly: SUPERCILEX/clipboard-history@28109d2 |
I've tested on both tempfile and xattr and I've seen no real issues. |
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. |
Rustix 1.0.0 is now released! Thanks to everyone who helped submit patches, bug reports, code reviews, and testing! |
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:
fs
module (details)rustix::fs::Access
consistent between linux_raw and libc backends (Port 1.0-staging to main #1152)mount_recursive_bind
tomount_bind_recursive
? Factor out a new top-levelmount
module. #763 (comment) (Renamemount_recursive_bind
tomount_bind_recursive
. #1273)SeekFrom::Hole
andSeekFrom::Data
's field fromi64
tou64
. (Make the offsets forSeekFrom
'sHole
andData
unsigned. #1266)Shutdown::ReadWrite
toShutdown::Both
to align with std (RenameShutdown::ReadWrite
toShutdown::Both
. #1264)features = ["extra_traits"]
from the libc dependency (Remove the "libc-extra-traits" feature. #1168)sched_yield
and othersched_*
functions fromprocess
tothread
, since they apply to threads rather than processes on Linux etc. (Movesched_*
andmembarrier_*
intorustix::thread
. #1265)stx_mtime
and similar members ofStatx
should bei64
, because Unix timestamps can be negative.futex
's first argument should beAtomic
get_
from sockopt getters, following Rust convention. Consider removingget_
in other things too. (Rename sockopts getters to remove the "get_". #1269)udata
argument torustix::event::kqueue::Event::new
should be a pointer instead of anisize
in order to better preserve provenance. (Make APIs preserve strict provenance. #1270)stx_attributes_mask
field ofStatx
with flags likelibc::STATX_ATTR_MOUNT_ROOT
should ideally be a bitflags, which requires makingStatx
a 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/orWaitId
to make the capitalization ofId
consistent (RenameWaidid*
toWaidId*
, for consistency withWaitId
. #1267)inotify_
prefixes from things in thefs::inotify
module.shm_
andShm
prefixes from things in theshm
module.recv
into an uninitialized buffer with theTRUNC
flag set (see Fixrecv_uninit
to handle theTRUNC
flag. #1159) (Report the number of received bytes inrecv_uninit
andrecvfrom_uninit
. #1278)io_uring_register_files_skip
from aconst fn
to a constant. (Replace theio_uring_register_files_skip
function with a constant. #1268)Deferring for now:
Dir
into its own crate, and have rustix exportgetdents
directly?open
andopenat
into separate functions for "create" which needs a mode vs. "open existing" which doesn't need a mode?RecvAncillaryBuffer::drain
always remove all messages, even if the iterator isn't exhausted. With that, we can remove theread_and_length
inAncillaryDrain
.rustix::cstr!
with something likerustix::nativestr!
so that users don't hard code "native strings are C strings" in their code?Arg::as_str
to avoid "a method with this name may be added to the standard library in the future" warningsrustix::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.Don't do these:
set_ip_add_membership
/get_ip_add_membership
should takeaddress
andifindex
arguments and*_with_ifindex
should be removed.ClockId::Uptime
on FreeBSD toBoottime
, since it's an aliasThe text was updated successfully, but these errors were encountered: