Skip to content

Fix link to implied bounds RFC. #553

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.

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
Mar 29, 2020
Merged
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion posts/inside-rust/2020-03-28-traits-sprint-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This Tuesday, the traits working group finished our first sprint of 2020, last 6

The overarching goal of the [traits working group][wg-traits] is to create a performant, extensible, and clean implementation of Rust's trait system. This implementation should scale not only to existing Rust features but also to new and upcoming features, such as:

* Implied bounds ([RFC](https://rust-lang.github.io/rfcs/2089-implied-bounds.md))
* Implied bounds ([RFC](https://rust-lang.github.io/rfcs/2089-implied-bounds.html))
* Const generics ([RFC](https://rust-lang.github.io/rfcs/2000-const-generics.html))
* Generic associated types (GATs) ([RFC](https://rust-lang.github.io/rfcs/1598-generic_associated_types.html))
* Inherent associated items ([tracking issue](https://github.com/rust-lang/rust/issues/8995))
Expand Down