Skip to content
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

update all dates in state-of-rust features table #156

Closed
wants to merge 1 commit into from
Closed

update all dates in state-of-rust features table #156

wants to merge 1 commit into from

Conversation

fbstj
Copy link
Contributor

@fbstj fbstj commented Jul 16, 2018

I've gone though each of the tracking issues and set the date to roughly the latest update, in some cases I've just chosen the latest comment, on others I've marked it as the assignment of the C-tracking-issue label (many of which were added by Mark Simulacrum on July 22nd 2017. I did explicitly ignore any of the link-back links below the last comment so in some cases (say the non-ASCII idents rust-lang/rust#28979) it is possibly out of date after the debate in June. Some of the latest comments dates may not count as 'updates'.

is it worth adding some indication as to when this list was last updated to the top-text, so these dates don't seem more stale than they are?

I've gone though each of the tracking issues and set the date to roughly the latest update, in some cases I've just chosen the latest comment, on others I've marked it as the assignment of the [C-tracking-issue](https://github.com/rust-lang/rust/labels/C-tracking-issue) label (many of which were added by Mark Simulacrum on July 22nd 2017. I did explicitly ignore any of the link-back links below the last comment so in some cases (say the non-ASCII idents rust-lang/rust#28979) it is possibly out of date after the debate in June. Some of the latest comments dates may not count as 'updates'.

is it worth adding some indication as to when this list was last updated to the top-text, so these dates don't seem more stale than they are?
@Mark-Simulacrum
Copy link
Member

cc @Aaronepower

We discussed this on the PR that added the dates and felt that it'd be more useful to know when the feature was looked at for this document, not when it was itself updated. As such I'm going to close.

@fbstj
Copy link
Contributor Author

fbstj commented Jul 16, 2018

ahh indeed that makes sense 👍 thanks for the explanation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants