Skip to content

Rename is_{string,boolean} to is_{str,bool} #127

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

Closed
wants to merge 1 commit into from

Conversation

shahn
Copy link

@shahn shahn commented Jul 30, 2016

This matches the rename of as_{string,boolean} to as_{str,bool}. Fixes
issue #126

This matches the rename of as_{string,boolean} to as_{str,bool}. Fixes
issue serde-rs#126
@dtolnay
Copy link
Member

dtolnay commented Jul 30, 2016

We cannot remove is_string and is_boolean until the next breaking release. Please change the doc comments to indicate that these are deprecated and add is_str and is_bool as new functions.

@oli-obk
Copy link
Member

oli-obk commented Jul 30, 2016

Are we on a new enough stable to support #[deprecated] ?

@dtolnay
Copy link
Member

dtolnay commented Jul 30, 2016

Unfortunately not, we have one release to go. The best we can do is probably:

#[doc(hidden)]
#[cfg_attr(feature = "unstable",
           deprecated(since = "0.8.1",
                      note="will be removed in 0.9.0; use is_str() instead"))]
fn

@shahn
Copy link
Author

shahn commented Aug 1, 2016

(Waiting on the discussion in #126 to update this PR)

@dtolnay
Copy link
Member

dtolnay commented Dec 24, 2016

Thanks for the PR. Based on #126 (comment) there is a justification for the current names. Also they are consistent with json-rust which famously has a more extensive and better-designed Value API than us, so it can't be so bad.

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

Successfully merging this pull request may close these issues.

3 participants