Update active RFC list from open issues in GitHub

[shepmaster]

I checked this list and grabbed the easy-to-parse RFC numbers and ensured they were in the active list.

[alexcrichton]

I think this RFC has long since been completed :)

[shepmaster]

@alexcrichton I'll let you rename subtask of RFC 59: Implement associated constants to the correct RFC ^_^.

[pnkfelix]

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.)

[alexcrichton]

Thanks! This list could probably do for an active GC as well, but that can also happen later.

[shepmaster]

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:

An RFC that makes it through the entire process to implementation is considered 'complete' and is moved to the 'complete' folder;

[shepmaster]

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!

[shepmaster]

I've removed the erroneous tilde RFC from the list, thanks @pnkfelix!

[alexcrichton]

An RFC that makes it through the entire process to implementation is considered 'complete' and is moved to the 'complete' folder;

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.

[shepmaster]

this is actually outdated information now, a completed RFC is just removed from the list.

@alexcrichton it's there on the README... maybe we need an RFC to update RFC #2 😇