summaryrefslogtreecommitdiff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2023-02-19 14:47:56 +0100
committerGitHub <noreply@github.com>2023-02-19 14:47:56 +0100
commitd2aef58eb515bde7b96a1875fa61ecf786b9f236 (patch)
tree6410bc6271f89ab188e545d0a418fef1f4dbae8b /tests/rustdoc-js-std/parser-errors.js
parent243dcd0083c6cfb5f6ead85315bd16e5844e6c86 (diff)
parent3e57b203918bc64e05c95849672ba7c23090c984 (diff)
downloadrust-d2aef58eb515bde7b96a1875fa61ecf786b9f236.tar.gz
Rollup merge of #108203 - compiler-errors:rpitit-fix-defaults-2, r=jackh726
Fix RPITITs in default trait methods (by assuming projection predicates in param-env) Instead of having special projection logic that allows us to turn `ProjectionTy(RPITIT, [Self#0, ...])` into `OpaqueTy(RPITIT, [Self#0, ...])`, we can instead augment the param-env of default trait method bodies to assume these as projection predicates. This should allow us to only project where we're allowed to! In order to make this work without introducing a bunch of cycle errors, we additionally tweak the `OpaqueTypeExpander` used by `ParamEnv::with_reveal_all_normalized` to not normalize the right-hand side of projection predicates. This should be fine, because if we use the projection predicate to normalize some other projection type, we'll continue to normalize the opaque that it gets projected to. This also makes it possible to support default trait methods with RPITITs in an associated-type based RPITIT lowering strategy without too much extra effort. Fixes #107002 Alternative to #108142
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions