diff options
| author | Evgeny Safronov <division494@gmail.com> | 2016-06-29 10:40:25 +0300 |
|---|---|---|
| committer | Evgeny Safronov <division494@gmail.com> | 2016-07-06 00:01:14 +0300 |
| commit | ede39aeb331bf6efb3739d22a60c1844e9c2c3d6 (patch) | |
| tree | bcd62c0edd6afb3fbd803e28c5f1cf627d97ede4 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | ea0dc9297283daff6486807f43e190b4eb561412 (diff) | |
| download | rust-ede39aeb331bf6efb3739d22a60c1844e9c2c3d6.tar.gz rust-ede39aeb331bf6efb3739d22a60c1844e9c2c3d6.zip | |
feat: reinterpret `precision` field for strings
This commit changes the behavior of formatting string arguments
with both width and precision fields set.
Documentation says that the `width` field is the "minimum width"
that the format should take up. If the value's string does not
fill up this many characters, then the padding specified by
fill/alignment will be used to take up the required space.
This is true for all formatted types except string, which is truncated
down to `precision` number of chars and then all of `fill`, `align` and
`width` fields are completely ignored.
For example: `format!("{:/^10.8}", "1234567890);` emits "12345678".
In the contrast Python version works as the expected:
```python
>>> '{:/^10.8}'.format('1234567890')
'/12345678/'
```
This commit gives back the `Python` behavior by changing the `precision`
field meaning to the truncation and nothing more. The result string *will*
be prepended/appended up to the `width` field with the proper `fill` char.
However, this is the breaking change.
Also updated `std::fmt` docs about string precision.
Signed-off-by: Evgeny Safronov <division494@gmail.com>
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
