| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
Rollup of 9 pull requests
Successful merges:
- #100293 (Add inline-llvm option for disabling/enabling LLVM inlining)
- #100767 (Remove manual <[u8]>::escape_ascii)
- #101668 (Suggest pub instead of public for const type item)
- #101671 (Fix naming format of IEEE 754 standard)
- #101676 (Check that the types in return position `impl Trait` in traits are well-formed)
- #101681 (Deny return-position `impl Trait` in traits for object safety)
- #101693 (Update browser UI test 0 10)
- #101701 (Rustdoc-Json: Add tests for trait impls.)
- #101706 (rustdoc: remove no-op `#search`)
Failed merges:
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Rustdoc-Json: Add tests for trait impls.
|
|
r=notriddle
Update browser UI test 0 10
The biggest change from this browser-ui-test update is the upgrade of the puppeteer version to `17.1.3` (the latest in short).
I also added the command `click-with-offset` to still allow us to click on the `[-]` part.
cc `@jsha`
r? `@notriddle`
|
|
Deny return-position `impl Trait` in traits for object safety
Fixes #101667
|
|
Check that the types in return position `impl Trait` in traits are well-formed
This effectively duplicates `check_associated_type_bounds`, but that shouldn't be for long, since we're going to remove it once we refactor RPITITs into regular associated items.
Fixes #101663
---
We don't check
```rust
trait Foo {
fn bar() -> impl ?Sized;
}
```
currently, but that's for a different reason, which is that we don't currently check that a trait function's return type is sized (i.e. `fn bar() -> [u8]` also works in a trait).
|
|
Suggest pub instead of public for const type item
Fixes #101626
|
|
Add inline-llvm option for disabling/enabling LLVM inlining
In this PR, a new -Z option `inline-llvm` is added in order to be able to turn on/off LLVM inlining.
The capability of turning on/off inlining in LLVM backend is needed for testing performance implications of using recently enabled inlining in rustc's frontend (with -Z inline-mir=yes option, #91743). It would be interesting to see the performance effect using rustc's frontend inlining only without LLVM inlining enabled. Currently LLVM is still doing inlining no mater what value inline-mir is set to. With the option `inline-llvm` being added in this PR, user can turn off LLVM inlining by using `-Z inline-llvm=no` option (the default of inline-llvm is 'yes', LLVM inlining enabled).
|
|
Fix ICE in opt_suggest_box_span
We were _totally_ mishandling substs and obligations in `opt_suggest_box_span`, so I reworked that function pretty heavily.
Also some drive-by changes, namely removing `ret_type_span`.
Fixes #101465
|
|
Avoid infinite loop in function arguments checking
Fixes #100478
Fixes #101097
|
|
|
|
Implement `std::marker::Tuple`
Split out from #99943 (https://github.com/rust-lang/rust/pull/99943#pullrequestreview-1064459183).
Implements part of rust-lang/compiler-team#537
r? `@jackh726`
|
|
|
|
|
|
|
|
|
|
Only encode return-position `impl Trait` in trait when parent function has a default body
Semi-blocked on #101679, because I can't currently write a test for when we _should_ encode the type of the return-position `impl Trait` in trait, which is when a trait has a default function body, like so:
```rust
trait Foo {
fn bar() -> impl Sized { }
}
```
Though this can land even without #101679, since it does prevent ICEs from occuring any time you use `#![feature(return_position_impl_trait_in_trait)]` in a library, which is kind annoying.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Simplify codeblock and their associated tooltip
It is based on https://github.com/rust-lang/rust/pull/101600 so it needs to wait for this one to be merged first.
This PR does two things:
* Remove CSS class duplication by setting CSS classes such as `compile_fail` directly on the `div` wrapping both the codeblock and the tooltip.
* Simplify DOM: no need to wrap the tooltip into a `<div>`, it can work just as well without it.
You can test it [here](https://rustdoc.crud.net/imperio/codeblock-tooltip/std/string/struct.String.html#deref).
r? `@notriddle`
|
|
Remove ReEmpty
r? rust-lang/types
|
|
Fix LLVM IR type mismatch reported in #99551
Closes #99551 .
|
|
Seems this doesn't trigger error on LLVM 15, but let's fix it for better compatibility.
|
|
rustdoc: avoid cleaning modules with duplicate names
Fixes #83375
|
|
remove bound var hack in `resolve`
somehow dropped that change from #98900.
r? `@jackh726`
|
|
The `<*const T>::guaranteed_*` methods now return an option for the unknown case
cc https://github.com/rust-lang/rust/issues/53020#issuecomment-1236932443
I chose `0` for "not equal" and `1` for "equal" and left `2` for the unknown case so backends can just forward to raw pointer equality and it works ✨
r? `@fee1-dead` or `@lcnr`
cc `@rust-lang/wg-const-eval`
|
|
|
|
Rollup of 6 pull requests
Successful merges:
- #101413 (Use RelocModel::Pic for UEFI targets)
- #101595 (Fix ICE report flags display.)
- #101616 (Adapt test for msan message change)
- #101624 (rustdoc: remove unused CSS `#search { position: relative }`)
- #101633 (Rustdoc-Json: Correcty handle intra-doc-links to items without HTML page)
- #101634 (Rustdoc-Json Tests: Use ``@is`` and ``@ismany`` more often.)
Failed merges:
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Rustdoc-Json Tests: Use `@is` and `@ismany` more often.
|
|
Rustdoc-Json: Correcty handle intra-doc-links to items without HTML page
Closes #101531
I renamed the `did` field in `ItemLink ` to more accurately describe what it does.
r? `@jyn514`
|
|
rustdoc: remove unused CSS `#search { position: relative }`
This was added in 611d0e6ccef8b60fa86ff5aa8fe3571cd36c444a, to allow its child `#results` element to be absolutely positioned inside it. The child stopped being absolute in 8c0469552e879f6319f8f96db660bab9eae1de5c.
To keep the layout looking the same, the links need to not have `width: 100%` any more, relying instead on the box naturally growing to fit because it has `display: block`.
|
|
Adapt test for msan message change
Similar to rust-lang/rust#100445, this adapts the new test added by rust-lang/rust#99207 to some relatively recent [LLVM changes](https://github.com/llvm/llvm-project/commit/057cabd997aeaef136e1e14f2ee645bd5bb197dd) that removed the function name from msan messages.
Found via our experimental rust + llvm @ HEAD bot:
https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/13347#018321b2-0cc3-4c91-b4db-774477e8b074
`@rustbot` label +llvm-main
|
|
r=petrochenkov
Use RelocModel::Pic for UEFI targets
In https://github.com/rust-lang/rust/pull/100537, the relocation model for UEFI targets was changed from PIC (the default value) to
static. There was some dicussion of this change here: https://github.com/rust-lang/rust/pull/100537#discussion_r952363012
It turns out that this can cause compilation to fail as described in https://github.com/rust-lang/rust/issues/101377, so switch back to PIC.
Fixes https://github.com/rust-lang/rust/issues/101377
|
|
Stabilize raw-dylib for non-x86
This stabilizes the `raw-dylib` and `link_ordinal` features (#58713) for non-x86 architectures (i.e., `x86_64`, `aarch64` and `thumbv7a`):
* Marked the `raw_dylib` feature as `active`.
* Marked the `link_ordinal` attribute as `ungated`.
* Added new errors if either feature is used on x86 targets without the `raw_dylib` feature being enabled.
* Updated tests to only set the `raw_dylib` feature when building for x86.
|
|
|
|
|
|
|
|
|
|
Closes #101531
|
|
Rollup of 5 pull requests
Successful merges:
- #101366 (Restore old behaviour on broken UNC paths)
- #101492 (Suggest adding array lengths to references to arrays if possible)
- #101529 (Fix the example code and doctest for Formatter::sign_plus)
- #101573 (update `ParamKindOrd`)
- #101612 (Fix code generation of `Rvalue::Repeat` with 128 bit values)
Failed merges:
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|