diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-04 07:54:30 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-04 07:54:30 +0200 |
| commit | 3e7d5aaef5ebd34355a87f2d1d65f02aa4b9d816 (patch) | |
| tree | a52f60b7c2f949e0009738ea24468946ec04a11b /compiler/rustc_codegen_gcc/example/std_example.rs | |
| parent | 792fc2b033aea7ea7b766e38bdc40f7d6bdce8c3 (diff) | |
| parent | 742014e7e3576f3053e7c63fc930c4d5b5b7a477 (diff) | |
| download | rust-3e7d5aaef5ebd34355a87f2d1d65f02aa4b9d816.tar.gz rust-3e7d5aaef5ebd34355a87f2d1d65f02aa4b9d816.zip | |
Rollup merge of #136687 - joshtriplett:improve-display-and-fromstr-docs, r=Amanieu
Improve the documentation of `Display` and `FromStr`, and their interactions In particular: - `Display` is not necessarily lossless - The output of `Display` might not be parseable by `FromStr`, and might not produce the same value if it is. - Calling `.parse()` on the output of `Display` is usually a mistake unless a type's documented output and input formats match. - The input formats accepted by `FromStr` depend on the type. This documentation adds no API surface area and makes no guarantees about stability. To the best of my knowledge, everything it says is already established to be true. As such, I don't think it needs an FCP.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/std_example.rs')
0 files changed, 0 insertions, 0 deletions