| Age | Commit message (Collapse) | Author | Lines |
|
|
|
These tasks used to depend on the iteration order of `module_children`.
|
|
|
|
Add a note about side effects for "peekable" iterators
|
|
Rollup of 10 pull requests
- Successful merges: #31441, #32956, #33003, #33022, #33023, #33032, #33039, #33044, #33045, #33046
- Failed merges:
|
|
Fix diagnostics for unresolved patterns
This fixes #33043, a bug in the diagnostics for unresolved patterns.
r? @eddyb
|
|
resolve: Refactor away `DefModifiers`
This refactors away `DefModifiers`, which is unneeded now that #32875 has landed.
r? @eddyb
|
|
syntax: Parse import prefixes as paths
Fixes https://github.com/rust-lang/rust/issues/10415
r? @eddyb
(This partially intersects with https://github.com/rust-lang/rust/pull/33041)
|
|
Adjust example for error E0225
Adjust example for error E0225
It's using Copy as a trait object compatible trait, which is not
appropriate, change to use a more typical Read + Send + Sync example.
Also use whitespace around `+`.
This seems appropriate apropos issue #32963
|
|
Update casting-between-types.md
|
|
Implement `Display` and `Hash` for `std::num::Wrapping`
Also, change the `Debug` implementation to only show the inner value.
Fixes #33006.
|
|
Fix f32::sin_cos and f64::sin_cos examples
|
|
Add examples for std::ptr module functions
Part of #29371.
r? @steveklabnik
|
|
Start documenting BTreeMap's node interface
cc @Gankro @apasel422
|
|
List possible keys of the -L rustc option.
Since `rustc --help -v` does not describe it, only *rustc.1* man page, but there is no man for Windows.
r? @alexcrichton
cc @steveklabnik
|
|
collections: add append for binary heap
|
|
std: Change String::truncate to panic less
The `Vec::truncate` method does not panic if the length argument is greater than
the vector's current length, but `String::truncate` will indeed panic. This
semantic difference can be a bit jarring (e.g. #32717), and after some
discussion the libs team concluded that although this can technically be a
breaking change it is almost undoubtedly not so in practice.
This commit changes the semantics of `String::truncate` to be a noop if
`new_len` is greater than the length of the current string.
Closes #32717
|
|
Get all (but one) of debuginfo tests to pass with MIR codegen.
I didn't get much feedback in #31005 so I went ahead and implemented something simple.
Closes #31005, as MIR debuginfo should work now for most usecases.
The `no-debug-attribute` test no longer assumes variables are in scope of `return`.
We might also want to revisit that in #32949, but the test is more reliable now either way.
In order to get one last function in the `associated-type` test pass, this PR also fixes #32790.
|
|
|
|
|
|
Remove unused trait imports
|
|
|
|
Implement `pub(restricted)` privacy (RFC 1422)
This implements `pub(restricted)` privacy from RFC 1422 (cc #32409) behind a feature gate.
`pub(restricted)` paths currently cannot use re-exported modules both for simplicity of implementation and for future compatibility with RFC 1560 (cf #31783).
r? @nikomatsakis
|
|
|
|
the feature `pub_restricted` is enabled.
|
|
It's using Copy as a trait object compatible trait, which is not
appropriate, change to use a more typical Read + Send + Sync example.
Also use whitespace around `+`.
|
|
|
|
|
|
slice: Add tracking issue for slice_binary_search_by_key
|
|
|
|
|
|
Also, change the `Debug` implementation to only show the inner value.
Fixes #33006.
|
|
|
|
Implement `Default` for more types in the standard library
Also add `Hash` to `std::cmp::Ordering` and most possible traits to
`fmt::Error`.
|
|
Add initial version of codegen unit partitioning for incremental compilation.
The task of the partitioning module is to take the complete set of translation items of a crate and produce a set of codegen units from it, where a codegen unit is a named set of (translation-item, linkage) pairs. That is, this module decides which translation item appears in which codegen units with which linkage.
This version only handles the case of partitioning for incremental compilation, not the regular N-codegen units case. In the future the regular case should be handled too, maybe even doing a bit more analysis to intelligently figure out a good partitioning.
One thing that could be improved is the syntax of the codegen unit tests. Right now they still use the compile-fail error specification infrastructure, so everything has to be on one line. Would be nice to be able to format things in a more readable way.
|
|
|
|
|
|
Rollup of 11 pull requests
- Successful merges: #32923, #32926, #32929, #32931, #32935, #32945, #32946, #32964, #32970, #32973, #32997
- Failed merges:
|
|
|
|
|
|
r=nagisa
alloc_system: Handle failure properly
The Unix implementation was incorrectly handling failure for reallocation of
over-aligned types by not checking for NULL.
Closes #32993
|
|
remove "#" symbols to make the code compile
|
|
Accommodate the case where dup lang items are entirely external.
Fixes #32961
|
|
doc: add missing comma
|
|
trans: always register an item's symbol, even if duplicated.
Fixes #32783 which was introduced by not always registering item symbols in #32742.
|
|
implement RFC amendment 1494
Adds `:block` to the follow set for `:ty` and `:path`. See rust-lang/rfcs#1494.
|
|
Restore trait impl docs
Currently, documentation on methods in trait implementations doesn't get rendered. This changes that; trait implementations have all documentation associated with impl items displayed (documentation from the trait definition is ignored).
Fixes #24838
Fixes #26871
|
|
deepak:gh-issue-32928-update-cargo-in-getting-started-doc, r=GuillaumeGomez
Doc fix: Update Cargo.toml in book/getting-started
The Cargo.toml mentioned in book/getting-started
is missing the section called `[dependencies]`
fixes https://github.com/rust-lang/rust/issues/32928
|
|
Update a comment to reflect changes in tidy checks.
|
|
rustbuild: Verify sha256 of downloaded tarballs
Here's a quick first pass at this.
I don't use Python often enough to claim that this is totally Pythonic. I've left off some (almost certainly unnecessary) error handling regarding opening and processing files. The whole tarball is read into memory to calculate the hash, but the file isn't *so* large so that should be fine. I don't care for the output from `raise RuntimeError`, but that's how `run()` does it so I'm following precedent.
Tested by manually changing the value of `expected`, and by modifying the tarball then forcing `rustc_out_of_date()`. Both cases tripped the error.
Closes https://github.com/rust-lang/rust/issues/32902
|