Skip to content

Fix div_duration() marked as stable by mistake #408

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 2 commits into from
Oct 1, 2019
Merged

Fix div_duration() marked as stable by mistake #408

merged 2 commits into from
Oct 1, 2019

Conversation

JMS55
Copy link
Contributor

@JMS55 JMS55 commented Sep 26, 2019

No description provided.

@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@nikomatsakis
Copy link
Contributor

Thanks ;)

Copy link
Contributor

@nikomatsakis nikomatsakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the PR! but I thnk the newlines aren't quite right. We probably want the "previous version" text to be in the same bullet as the strikeout text, and there is a missing newline before the non-striked-out text

image

@Mark-Simulacrum
Copy link
Member

I think we usually just fix things without mentioning that they were previously wrong -- maybe it's worth sticking that in a footnote, but not more than that. Could you update the post as such?

@JMS55
Copy link
Contributor Author

JMS55 commented Sep 26, 2019

Thank you for catching that my previous suggestion had messed-up formatting. In the second commit I moved it down to a footnote at the end instead. I'm not sure if Corrections is self-explanatory enough, but otherwise I think it's good.

@@ -95,8 +95,8 @@ Additionally, these functions have been stabilized:

- [`<*const T>::cast`] and [`<*mut T>::cast`]
- [`Duration::as_secs_f32`] and [`Duration::as_secs_f64`]
- [`Duration::div_duration_f32`] and [`Duration::div_duration_f64`]
- [`Duration::div_f32`] and [`Duration::div_f64`]
- EDIT: A Previous version of this post mistakenly marked these as stable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @Mark-Simulacrum noted, no need to retain the "historical record" here -- just remove the incorrect item from the list.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure what you mean, I did remove it. I think your looking at the older commit maybe? Sorry, I'm new to github.

Copy link
Contributor

@nikomatsakis nikomatsakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what was going on, but it looks good now! Thanks.

@nikomatsakis nikomatsakis merged commit a0a6fb7 into rust-lang:master Oct 1, 2019
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.

4 participants