diff options
| author | bors <bors@rust-lang.org> | 2024-05-18 08:44:01 +0000 | 
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-05-18 08:44:01 +0000 | 
| commit | 1c90b9fe6eac122b4d3965913b3615f47751a4d3 (patch) | |
| tree | f18822d80aba5f4a47965ce7ac9a3fe6d0279269 /src/doc/rustdoc | |
| parent | 36c0a6d40fb6aae9c450305085d64e2ba55c6c58 (diff) | |
| parent | 582fd1fb539ddea199dbc238946b00465a20620e (diff) | |
| download | rust-1c90b9fe6eac122b4d3965913b3615f47751a4d3.tar.gz rust-1c90b9fe6eac122b4d3965913b3615f47751a4d3.zip  | |
Auto merge of #125004 - pymongo:issue-125002, r=estebank
Fix println! ICE when parsing percent prefix number
This PR fixes #125002 ICE occurring, for example, with `println!("%100000", 1)` or `println!("%    100000", 1)`.
## Test Case/Change Explanation
The return type of `Num::from_str` has been changed to `Option<Self>` to handle errors when parsing large integers fails.
1. The first `println!` in the test case covers the change of the first `Num::from_str` usage in `format_foreign.rs:426`.
2. The second `println!` in the test case covers the change of the second `Num::from_str` usage in line 460.
3. The 3rd to 5th `Num::from_str` usages behave the same as before.
The 3rd usage would cause an ICE when `num > u16::MAX` in the previous version, but this commit does not include a fix for the ICE in `println!("{:100000$}")`. I think we need to emit an error in the compiler and have more discussion in another issue/PR.
Diffstat (limited to 'src/doc/rustdoc')
0 files changed, 0 insertions, 0 deletions
