-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollup of 17 pull requests #74230
Rollup of 17 pull requests #74230
Conversation
Co-authored-by: Teymour Aldridge <[email protected]>
This patch adds `VecDeque::range` and `VecDeque::range_mut` to provide iterators over a sub-range of a `VecDeque`. This behavior can be emulated with `skip` and `take`, but directly providing a `Range` is more ergonomic. This also partially makes up for `VecDeque`'s lack of `SliceIndex` support.
A function that has no prologue cannot be reasonably expected to support debuginfo. In fact, the existing code (before this patch) would generate invalid instructions that caused crashes. We can solve this easily by just not emitting the debuginfo in this case. Fixes rust-lang#42779 cc rust-lang#32408
This pulls in a fix for the install script on some tr(1) implementations, as well as an update to use `anyhow` instead of `failure` for error handling.
This adds `read_exact_at` and `write_all_at` to WASI's `FileExt`, similar to the Unix versions of the same names.
Rename the existing read_at/write_at to read_vectored_at/write_vectored_at, for consistency with libstd's read_vectored/write_vectored. And, introduce new read_at/write_at functions which take a single buffer, similar to all other targets which provide these functions, so this will make it easier for applications to share code between WASI and other targets. Note that WASI's FileExt is currently unstable.
Suggested by @bjorn3 Every RUN command creates a new overlay on top of the image as of before the RUN command. Using fewer RUN commands prevents intermediate overlays (which in this case would have contained the entire Linux source tree).
When the dockerfiles were moved into the host-x86_64 directory, paths for COPY commands were updated with the new host-x86_64/ prefix. This suggested that the intended context was src/ci/docker. However, the context for disabled docker images was src/ci/docker/host-x86_64. This broke the new paths and prevented src/ci/docker/scripts from being included in the context at all. This commit corrects this context allowing docker to find the files it needs for COPY commands.
It has a single call site and having it as a separate (higher-order!) function makes the code harder to read.
This makes the two versions (parallel and non-parallel) more similar to each other.
A couple of these are quite long, but they do a much better job of explaining what they do, which was non-obvious before.
This commit replaces the use of `trim_start_matches` because in `rustc -Vv` output there are no lines starting with multiple "release:".
@bors r+ p=30 rollup=never |
📌 Commit 6475176 has been approved by |
⌛ Testing commit 6475176 with merge 950fb228cfe5b6b008b3b0a7b21fb0cade64d940... |
💔 Test failed - checks-actions |
@bors retry network |
⌛ Testing commit 6475176 with merge bf04e78300753264de115ed1eb8fb3e0c2421f76... |
💥 Test timed out |
@bors retry |
⌛ Testing commit 6475176 with merge f4c29df54623294b311d53c8213920618563fc6d... |
Okay, that's actually #74105 (comment) |
@bors r- retry yield |
Successful merges:
&[T]
in const fn #73862 (Stabilize casts and coercions to&[T]
in const fn)read_exact_at
andwrite_all_at
to WASI'sFileExt
#74076 (Addread_exact_at
andwrite_all_at
to WASI'sFileExt
)windows-msvc
targets #74103 (Only add CFGuard onwindows-msvc
targets)repr(i128/u128)
on enum #74109 (Only allowrepr(i128/u128)
on enum)Failed merges:
r? @ghost