| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-01-08 | `all` to `any` | lcnr | -5/+5 | |
| don't really know why, but it is a lot easier for me to think about cycles that way. | ||||
| 2024-01-08 | do not track root depth of cycles | lcnr | -37/+32 | |
| results in slightly cleaner logic while making the following commit easier | ||||
| 2024-01-08 | use doc comments | lcnr | -3/+3 | |
| 2024-01-08 | Auto merge of #119693 - petrochenkov:cachemark, r=cjgillot | bors | -5/+14 | |
| macro_rules: Add an expansion-local cache to span marker Most tokens in a macro body typically have the same syntax context. So the cache should usually be hit. This change can either be combined with https://github.com/rust-lang/rust/pull/119689, or serve as its alternative, depending on perf results. | ||||
| 2024-01-08 | macro_rules: Add an expansion-local cache to span marker | Vadim Petrochenkov | -5/+14 | |
| 2024-01-08 | Auto merge of #119722 - matthiaskrgr:rollup-y6w3c9h, r=matthiaskrgr | bors | -597/+1499 | |
| Rollup of 5 pull requests Successful merges: - #116129 (Rewrite `pin` module documentation to clarify usage and invariants) - #119703 (Impl trait diagnostic tweaks) - #119705 (Support `~const` in associated functions in trait impls) - #119708 (Unions are not `PointerLike`) - #119711 (Delete unused makefile in tests/ui) r? `@ghost` `@rustbot` modify labels: rollup | ||||
| 2024-01-08 | Rollup merge of #119711 - Nilstrieb:makewtf, r=WaffleLapkin | Matthias Krüger | -8/+0 | |
| Delete unused makefile in tests/ui ?????????? | ||||
| 2024-01-08 | Rollup merge of #119708 - compiler-errors:pointer-like, r=Nilstrieb | Matthias Krüger | -2/+38 | |
| Unions are not `PointerLike` I introduced the `PointerLike` trait to enforce `dyn*` coercions only from types that share the same ABI as a pointer. On top of needing to be scalar, they also should not be unions, since CTFE chokes on scalar reads for union types. Fixes #119695 | ||||
| 2024-01-08 | Rollup merge of #119705 - fmease:tilde-const-assoc-fns-trait-impls, ↵ | Matthias Krüger | -30/+65 | |
| r=compiler-errors Support `~const` in associated functions in trait impls Fixes #119700. | ||||
| 2024-01-08 | Rollup merge of #119703 - compiler-errors:impl-trait-tweaks, r=fmease | Matthias Krüger | -182/+292 | |
| Impl trait diagnostic tweaks 1. Tweak some names for `impl Trait` being used in the wrong position 2. Remove two helper functions that are no longer needed since RPITIT is stable, and which causes matches to be a bit obtuse. 3. Split and fix the part where the error notes that it's "only allowed in XX" Fixes #119629 | ||||
| 2024-01-08 | Rollup merge of #116129 - fu5ha:better-pin-docs-2, r=Amanieu | Matthias Krüger | -375/+1104 | |
| Rewrite `pin` module documentation to clarify usage and invariants The documentation of `pin` today does not give a complete treatment of pinning from first principles, nor does it adequately help build intuition and understanding for how the different elements of the pinning story fit together. This rewrite attempts to address these in a way that makes the concept more approachable while also making the documentation more normative. This PR picks up where `@mcy` left off in #88500 (thanks to him for the original work and `@Manishearth` for mentioning it such that I originally found it). I've directly incorporated much of the feedback left on the original PR and have rewritten and changed some of the main conceits of the prose to better adhere to the feedback from the reviewers on that PR or just explain something in (hopefully) a better way. | ||||
| 2024-01-07 | Delete unused makefile in tests/ui | Nilstrieb | -8/+0 | |
| ?????????? | ||||
| 2024-01-07 | Unions are not PointerLike | Michael Goulet | -2/+38 | |
| 2024-01-07 | Split note, fix const/static impl trait error | Michael Goulet | -129/+257 | |
| 2024-01-07 | effects: support ~const in assoc fns in trait impls | León Orell Valerian Liehr | -30/+65 | |
| 2024-01-07 | link | Manish Goregaokar | -1/+1 | |
| 2024-01-07 | Update library/core/src/pin.rs | Manish Goregaokar | -1/+1 | |
| Co-authored-by: Ralf Jung <post@ralfj.de> | ||||
| 2024-01-07 | clean up structural pinning | Manish Goregaokar | -8/+10 | |
| 2024-01-07 | footnote on dropping futures | Manish Goregaokar | -2/+5 | |
| 2024-01-07 | valid | Manish Goregaokar | -1/+1 | |
| 2024-01-07 | punctuation in parens | Manish Goregaokar | -2/+2 | |
| 2024-01-07 | Apply suggestions from code review | Manish Goregaokar | -4/+4 | |
| Co-authored-by: Ralf Jung <post@ralfj.de> Co-authored-by: Daniel Henry-Mantilla <daniel.henry.mantilla@gmail.com> | ||||
| 2024-01-07 | Clean up guarantees wording | Manish Goregaokar | -15/+7 | |
| We don't need to go into that much depth at this stage | ||||
| 2024-01-07 | lifetime -> lifespan where relevant. improve docs on as_ref() | Manish Goregaokar | -6/+6 | |
| 2024-01-07 | Rephrase unpin docs in terms of pinning-agnosticness | Manish Goregaokar | -4/+6 | |
| 2024-01-07 | trim section on managed-box model | Gray Olson | -9/+4 | |
| 2024-01-07 | improve `Pin::new_unchecked` docs | Gray Olson | -10/+16 | |
| 2024-01-07 | update ui tests | Gray Olson | -5/+5 | |
| 2024-01-07 | fix broken link | Gray Olson | -1/+1 | |
| 2024-01-07 | justify motivation of `Unpin` better | Gray Olson | -14/+30 | |
| 2024-01-07 | improve `Pin` and `Pin::new` docs | Gray Olson | -23/+67 | |
| 2024-01-07 | `Pin<P>` -> `Pin<Ptr>` | Gray Olson | -75/+81 | |
| 2024-01-07 | fix typos and edit prose | Gray Olson | -76/+85 | |
| 2024-01-07 | edit new section for typos and better wording | Gray Olson | -16/+21 | |
| 2024-01-07 | fix imports | Gray Olson | -6/+5 | |
| 2024-01-07 | fix typos | Gray Olson | -4/+4 | |
| 2024-01-07 | add section on manual owning ptr managed solution via @kpreid | Gray Olson | -9/+36 | |
| 2024-01-07 | improve structural Unpin + formatting | Gray Olson | -8/+10 | |
| 2024-01-07 | reword unpin auto impl section | Gray Olson | -26/+20 | |
| 2024-01-07 | fix link in footnote | Gray Olson | -3/+3 | |
| 2024-01-07 | improve `Pin` struct docs and add examples | Gray Olson | -8/+89 | |
| 2024-01-07 | improve intro and discussion of pinning as library contract | Gray Olson | -39/+59 | |
| 2024-01-07 | improve intro and `Unpin`-related discussion | Gray Olson | -67/+145 | |
| 2024-01-07 | update doubly linked list commentary and fix links | Gray Olson | -19/+26 | |
| 2024-01-07 | fix one more broken link | Gray Olson | -1/+1 | |
| 2024-01-07 | fix broken links | Gray Olson | -2/+2 | |
| 2024-01-07 | Fix examples, finish polishing | Gray Olson | -48/+87 | |
| 2024-01-07 | mostly done | Gray Olson | -348/+359 | |
| 2024-01-07 | Rewrite `Pin<P>` docs to clarify guarantees and uses | Miguel Young de la Sota | -214/+605 | |
| The documentation today does not give a complete treatment of pinning from first principles, which appropriately describes how to design types that use it, nor does it provide formal statements of the guarantees users need to be aware of. This rewrite attempts to address these in a way that makes the concept more approachable while also making the documentation more normative. | ||||
| 2024-01-07 | Inline some helpers no longer needed due to RPITIT being stable | Michael Goulet | -47/+29 | |
