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

Correct handling of non-numeric chars in parse_buf #1106

Closed
wants to merge 2 commits into from

Conversation

mbrubeck
Copy link
Contributor

Without this fix, int::parse_buf and uint::parse_buf return incorrect results for any strings that contain non-numeric characters. Fixes #1102.

Without this fix, int::parse_buf and uint::parse_buf return incorrect results
for any strings that contain non-numeric characters.  Fixes rust-lang#1102.
@mbrubeck
Copy link
Contributor Author

Sure, how about this?

@marijnh
Copy link
Contributor

marijnh commented Oct 31, 2011

Cool. Integrated.

@marijnh marijnh closed this Oct 31, 2011
bjorn3 added a commit to bjorn3/rust that referenced this pull request Nov 27, 2020
coastalwhite pushed a commit to coastalwhite/rust that referenced this pull request Aug 5, 2023
celinval added a commit to celinval/rust-dev that referenced this pull request Jun 4, 2024
* Remove unused --allow-cbmc-verification-failure flag

* Cleaning up the kani arguments.

- Removed --auto-unwind which as broken.
- Fixed punctuation to be consistent.
- Hide unstable / developer features from short help.

* Fix --unwind conflict check

We were not covering any other form of unwind. Note that this will also
conflict with --unwinding-assertions which I think is probably fine
since we have that option in Kani.
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.

int::from_str("-1") == -253 and other bugs
2 participants