diff options
| author | bors <bors@rust-lang.org> | 2023-02-13 16:50:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-02-13 16:50:33 +0000 |
| commit | 42d4bd7d18f6db6686f0420dfc2e8574d66f09d2 (patch) | |
| tree | 30ac12490f2a7bc875fcfeba5d67d38b32257ab4 /tests/rustdoc-js-std/parser-errors.js | |
| parent | b3077fbc090049d9ac3c6299e5e3c08da09f2e08 (diff) | |
| parent | 340d9e818a5139c842edf7859cd3aba9361f4e08 (diff) | |
| download | rust-42d4bd7d18f6db6686f0420dfc2e8574d66f09d2.tar.gz rust-42d4bd7d18f6db6686f0420dfc2e8574d66f09d2.zip | |
Auto merge of #107924 - eggyal:move_fold_visit_traits_to_type_lib_with_trait_alias, r=oli-obk
Move folding & visiting traits into type library This is a rework of #107712, following feedback on that PR. In particular, this version uses trait aliases to reduce the API churn for trait consumers. Doing so requires a workaround for #107747 until its fix in #107803 is merged into the stage0 compiler; this workaround, which uses conditional compilation based on the `bootstrap` configuration predicate, sits in dedicated commit b409329c for ease of reversion. The possibility of the `rustc_middle` crate retaining its own distinct versions of each folding/visiting trait, blanket-implemented on all types that implement the respective trait in the type library, was also explored: however since this would necessitate making each `rustc_middle` trait a subtrait of the respective type library trait (so that such blanket implementations can delegate their generic methods), no benefit would be gained. r? types
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions
