| Age | Commit message (Collapse) | Author | Lines |
|---|
|
It currently reports net size, i.e. size(output) - size(input). After
some use I think this is sub-optimal, and it's better to just report
size(output). Because for derive macros the input size is always 1, and
for attribute macros it's almost always 1.
|
|
Because in the case of for example
pub fn my_fn3(f: impl FnMut()) {}
we want to keep `()` even if it is empty since that matches e.g. Rust
syntax requirements.
|
|
|
|
Fix comment on NoMangle
Fix comment on NoMangle.
This was discussed in comments of https://github.com/rust-lang/rust/pull/142823#discussion_r2162219576 and https://github.com/rust-lang/rust/pull/142921
|
|
Fix install-template.sh for Solaris tr
Allow to run install.sh also on Solaris where tr is not GNU tr.
|
|
Move error code explanation removal check into tidy
Follow-up of https://github.com/rust-lang/rust/pull/142677.
This PR replaces a shell script with rust code.
r? ghost
|
|
test(s) or bin at keyboard cursor
|
|
In an interactive context, the subprocess inherited a real tty stdin,
which lead it it waiting for something to happen, even though nothing
happened. By explicitly passing null as stdin we make sure an empty file
is passed, which achieves the desired behavior.
|
|
Co-authored-by: Folkert de Vries <folkert@folkertdev.nl>
|
|
|
|
docs: Add troubleshooting FAQ to the book
|
|
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
|
|
And one frequently asked question.
|
|
|
|
|
|
Subtree update of `rust-analyzer`
r? `@ghost`
|
|
|
|
|
|
|
|
|
|
`redundant_explicit_links` new API
|
|
|
|
from expansion
|
|
Rollup of 5 pull requests
Successful merges:
- rust-lang/rust#142493 (rework `#[naked]` attribute parser)
- rust-lang/rust#142636 (bootstrap.example.toml: use less contextual format)
- rust-lang/rust#142822 (Make `PartialEq` a `const_trait`)
- rust-lang/rust#142892 (Fix ICE on debug builds where lints are delayed on the crate root)
- rust-lang/rust#142904 (notify me when rdg is touched)
Failed merges:
- rust-lang/rust#142827 (Move error code explanation removal check into tidy)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
fix: Fix cargo project manifest not pointing to the workspace root
|
|
|
|
These tests have expanded beyond the RFC, so rename the directory
`rfc-3086-metavar-expr` to `metavar-expressions`. `concat` (which wasn't
part of the RFC) now fits in this group, so merge its tests into the
`metavar-expressions` directory.
Additionally rename some related `issue-*` tests.
|
|
|
|
|
|
|
|
bootstrap.example.toml: use less contextual format
prefixing each key with its section means you don't need to scroll up 4 pages to see which section
a particular key is from.
target specific options were kept in old format since the exact section name depends on the target, so those options must now be moved to the bottom of the file.
[inspired by zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/consider.20rewriting.20bootstrap.2Eexample.2Etoml.20to.20use.20section.2Ekey/with/521734873)
r? ``@workingjubilee``
|
|
|
|
Bump the version number to 1.90.0
Part of the release process. This PR must not be rolled up.
r? cuviper
|
|
|
|
|
|
|
|
|
|
|
|
`compiler` path
It was confusing that the `Rustc` step was invoked twice, once with all crates and once with no crates (even though both of these mean the same thing).
|
|
|
|
Rollup of 5 pull requests
Successful merges:
- rust-lang/rust#141597 (Document subdirectories of UI tests with README files)
- rust-lang/rust#142823 (Port `#[no_mangle]` to new attribute parsing infrastructure)
- rust-lang/rust#142828 (1.88.0 release notes)
- rust-lang/rust#142854 (centralize `-Zmin-function-alignment` logic)
- rust-lang/rust#142875 (Check rustdoc-json-types FORMAT_VERSION is correctly updated)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
faster string parsing
|
|
r=Kobzol
Check rustdoc-json-types FORMAT_VERSION is correctly updated
Follow-up of https://github.com/rust-lang/rust/pull/142677.
``@nnethercote`` suggested that we should also ensure that the `FORMAT_VERSION` was only increased by 1 and we should check for it, this PR does it.
cc ``@aDotInTheVoid``
r? ghost
|
|
Port `#[no_mangle]` to new attribute parsing infrastructure
Ports `no_mangle` to the new attribute parsing infrastructure for https://github.com/rust-lang/rust/issues/131229#issuecomment-2971353197
r? ``@jdonszelmann``
|
|
Document subdirectories of UI tests with README files
Part of rust-lang/rust#133895 and the [2025 Google Summer of Code](https://blog.rust-lang.org/2025/05/08/gsoc-2025-selected-projects/) associated project.
When adding a new UI test, one is faced with hundreds of subdirectories in `tests/ui` reflecting various categories. Knowing where to put the new test is not trivial, as many of the categories have slightly misleading names. For example, `moves` does not only refer to the `move` keyword but to functions taking ownership in general, whereas `allocator` does not refer to allocation in general but rather to the very specific `allocator_api` and `global_allocator` features.
Many contributors will therefore place their test at the top level of ̀`tests/ui` where it will be mixed with hundreds of unrelated tests.
This PR is a tentative move towards more clearly defined tag/categories, with a SUMMARY.md file documenting the true purpose of each subdirectory, placed inside `tests/ui`.
r? ``@jieyouxu``
|
|
|
|
|
|
the right type
|
|
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
|
|
The skipped test passes since nightly-2024-11-29. Let's stop skipping
it to increase the chance of detecing a regression.
|
