| Age | Commit message (Collapse) | Author | Lines |
|
E0423 doesn't apply only to structs, update the error index description
to make this clear.
|
|
Optimize layout calculations in HashMap
This now produces the same assembly code as the previous implementation.
cc #51163 @nnethercote @gnzlbg @andjo403
|
|
This now produces the same assembly code as the previous implementation.
|
|
Do not promote union field accesses
r? @eddyb
technically a breaking change, but the code errored on the previous stable and produces UB + a warning on the current stable. I don't think we need a crater run in that case.
|
|
docs order
See https://github.com/rust-lang/rust/issues/47115#issuecomment-392532855
|
|
Rollup of 6 pull requests
Successful merges:
- #51288 (Remove rustdoc-specific is_import field from HIR)
- #51299 (const fn integer operations)
- #51317 (Allow enabling incremental via config.toml)
- #51323 (Generate br for all two target SwitchInts)
- #51326 (Various minor slice iterator cleanups)
- #51329 (Remove the unused `-Z trans-time-graph` flag.)
Failed merges:
|
|
Remove the unused `-Z trans-time-graph` flag.
Rebase of #50783 has accidentally revived the flag (which should be renamed to `-Z codegen-time-graph` by #50615).
|
|
Various minor slice iterator cleanups
See individual commits
|
|
Generate br for all two target SwitchInts
Instead of only for booleans. This means that `if let` also becomes a br.
Apart from making the IR slightly simpler, this is supported by FastISel (#4353).
|
|
Allow enabling incremental via config.toml
r? @QuietMisdreavus
|
|
const fn integer operations
A follow up to #51171
Fixes #51267
Makes a lot of the integer methods (`swap_bytes`, `count_ones` etc) `const fn`s. See #51267 for a discussion about why this is wanted and the solution used.
|
|
Remove rustdoc-specific is_import field from HIR
Fixes #47100.
I believe that there is no need to check for the name being the same, as this
part of rustdoc seems to be strictly interested in exploring "public modules."
Re-exports from the same module cannot visit another module; and, re-exports
cannot export items with a greater visibility than that item declares.
Therefore, I think this code is either sufficient, or in fact does more than
is necessary, depending on whether rustdoc cares about the re-export itself.
r? @eddyb
|
|
r=GuillaumeGomez
Point to the rustdoc attribute where intralink resolution failed.
|
|
implement #[panic_implementation]
This implements the `#[panic_implementation]` attribute as instructed in https://github.com/rust-lang/rust/issues/44489#issuecomment-381324623
I haven't run the full test suite yet but at least all the compile-fail tests pass.
r? @nagisa
|
|
|
|
|
|
|
|
Clean up dependency tracking in Rustbuild [1/2]
Initial refactor of the `Mode` enum. Still a WIP
Ref #50509
r? @Mark-Simulacrum
|
|
Rebase of #50783 has accidentally revived the flag (which should be
renamed to `-Z codegen-time-graph` by #50615).
|
|
|
|
make is_tool inherent prop of mode
fix errors from rebase
resolve issues from review
|
|
|
|
These don't exist anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not required because this is a Rust function
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Rollup of 6 pull requests
Successful merges:
- #51143 (Specify that packed types must derive, not implement, Copy)
- #51226 (Make Layout's align a NonZeroUsize)
- #51297 (Fix run button style)
- #51306 (impl Default for &mut str)
- #51312 (Clarify the difference between get_mut and into_mut for OccupiedEntry)
- #51313 (use type name in E0599 enum variant suggestion)
Failed merges:
|
|
|
|
|
|
|
|
|
|
use type name in E0599 enum variant suggestion
Also, rename the variable from "type_str" to "item_kind" to avoid
the ambiguity that caused this bug.
|
|
Clarify the difference between get_mut and into_mut for OccupiedEntry
The examples for both hash_map::OccupiedEntry::get_mut and
hash_map::OccupiedEntry::into_mut were almost identical. This led to some
confusion over the difference, namely why you would ever use get_mut when
into_mut gives alonger lifetime. Reddit thread:
https://www.reddit.com/r/rust/comments/8a5swr/why_does_hashmaps
This commit adds two lines and a comment to the example, to show that the
entry object can be re-used after calling get_mut.
Closes https://github.com/rust-lang/rust/issues/49745
|
|
impl Default for &mut str
Rationale: There is already `impl Default for &mut [T]`.
Note: This impl is insta-stable.
|
|
Fix run button style
r? @QuietMisdreavus
|