Update active RFC list from open issues in GitHub #868
Conversation
| @@ -23,6 +23,7 @@ the direction the language is evolving in. | |||
| * [0016-more-attributes.md](text/0016-more-attributes.md) | |||
| * [0019-opt-in-builtin-traits.md](text/0019-opt-in-builtin-traits.md) | |||
| * [0048-traits.md](text/0048-traits.md) | |||
| * [0059-remove-tilde.md](text/0059-remove-tilde.md) | |||
There was a problem hiding this comment.
I think this RFC has long since been completed :)
There was a problem hiding this comment.
@alexcrichton I'll let you rename subtask of RFC 59: Implement associated constants to the correct RFC ^_^.
There was a problem hiding this comment.
Its a subtask of RFC #195. (When rust-lang/rust#17841 was filed, we were using a different RFC numbering scheme.)
(I have now renamed the linked issue in the rust repo.)
|
Thanks! This list could probably do for an active GC as well, but that can also happen later. |
|
I'd be happy to do a second cleanup of the list, basically it should be everything that doesn't have an open Rust issue, right? If all those issues had RFC numbers, it'd be easy for me to split the list. However, there is no "complete" folder:
|
|
I'd offer to rename the issue titles to add / correct RFC numbers in the Rust repo, but I'm pretty sure that is a bigger privilege that you don't want to hand out to too many people! |
e61a57b to
f7b5b83
Compare
|
I've removed the erroneous tilde RFC from the list, thanks @pnkfelix! |
Oh this is actually outdated information now, a completed RFC is just removed from the list. This looks good to me for now though! I'll to a GC right now to see if I can prune out some pieces. |
Update active RFC list from open issues in GitHub
@alexcrichton it's there on the README... maybe we need an RFC to update RFC #2 😇 |
I checked this list and grabbed the easy-to-parse RFC numbers and ensured they were in the active list.