aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_hir_ty/src
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2020-04-15 10:19:46 +0100
committerGitHub <[email protected]>2020-04-15 10:19:46 +0100
commitd61909f9047ba94c4ed9af580193958257ab21e6 (patch)
tree90606344bde7de8ced61085649e30255eac10603 /crates/ra_hir_ty/src
parent9726401eaed82b0afc51ea26f1789f435e906b47 (diff)
parent2e7b88b5256bd6c51226b63b93481a77ac901e14 (diff)
parentdb32a2e4211f9444ef4f10b633e400d27ed2662e (diff)
parentd88d67819b3f052422ad3f024e44ad73dde1630b (diff)
Merge #3964 #3965 #3967
3964: Nicer Chalk debug logs r=matklad a=flodiebold I'm looking at a lot of Chalk debug logs at the moment, so here's a few changes to make them slightly nicer... 3965: Implement inline associated type bounds r=matklad a=flodiebold Like `Iterator<Item: SomeTrait>`. This is an unstable feature, but it's used in the standard library e.g. in the definition of Flatten, so we can't get away with not implementing it :) (This is cherry-picked from my recursive solver branch, where it works better, but I did manage to write a test that works with the current Chalk solver as well...) 3967: Handle `Self::Type` in trait definitions when referring to own associated type r=matklad a=flodiebold It was implemented for other generic parameters for the trait, but not for `Self`. (Last one off my recursive solver branch :smile: ) Co-authored-by: Florian Diebold <[email protected]>