Skip to content

fix typos in 2024-06-26-types-team-update.md #1347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 26, 2024
Merged

fix typos in 2024-06-26-types-team-update.md #1347

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions posts/2024-06-26-types-team-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ the new implementation.
### Async and `impl Trait`

We stabilized `async`-fn in traits (AFIT) and return-position `impl Trait` in
traits (RPTIIT) in version 1.75 thanks to a significant effort by [@compiler-errors] and
traits (RPITIT) in version 1.75 thanks to a significant effort by [@compiler-errors] and
[@spastorino]. [@cjgillot] greatly improved the way generators, and therefore async functions,
are represented in the type system[^107421]. This allowed us to support recursive
`async`-functions without too much additional work[^117703].
Expand Down Expand Up @@ -134,7 +134,7 @@ We are also working on extracting its implementation into a separate library
outside of the compiler itself. We would like to share the trait solver with
rust-analyzer by the end of this year. They currently use [chalk] which is no longer
actively maintained. Using the next-generation trait solver in rust-analyzer
should result in a lot of additional testing for the solver and while also improving
should result in a lot of additional testing for the solver while also improving
the IDE experience by positively impacting performance and correctness.

We intend to slowly roll out the solver in other areas of the compiler until we're able
Expand Down