rust/library/core/src/fmt/mod.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-20T13:34:04+00:00Rollup merge of #143423 - hkBst:clippy-fix-1, r=workingjubilee2025-07-20T13:34:04+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-07-20T13:34:04+00:00urn:sha1:5ba1251b55ed560aabf92c81db6a6612de5f648e
address clippy formatting nits
- int_log10.rs: change top level doc comments to outer
- collect.rs: remove empty line after doc comment
- clippy fix: markdown indentation for indented items after line break: a markdown list item continued over multiples lines, but those following lines which are part of the same item are not indented
- clippy fix: bound in one place: when there is a bound in angle brackets and another bound on the same variable in a where clause
Rollup merge of #143426 - hkBst:clippy-fix-indent-1, r=jhpratt2025-07-09T03:50:27+00:00Trevor Grosst.gross35@gmail.com2025-07-09T03:50:27+00:00urn:sha1:0d99b5585b5f0d69f162472a83134e277a6c3839
clippy fix: indentation
Fixes indentation of markdown comments.
collect.rs: remove empty line after doc comment2025-07-08T11:48:15+00:00Marijn Schoutenmhkbst@gmail.com2025-07-02T13:29:16+00:00urn:sha1:f96d5d960256557a0c2434a308fd32c98e94aa7fclippy fix: indentation2025-07-04T11:52:17+00:00Marijn Schoutenmhkbst@gmail.com2025-07-04T11:33:36+00:00urn:sha1:1a1b52acbf44f55f7458dd38b260479843fe3810Implement `int_format_into` feature2025-07-03T16:57:16+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-06-05T21:29:03+00:00urn:sha1:82c6037b2adac3032191e76098774a334550ead2Remove some unsized tuple impls now that we don't support unsizing tuples anymore2025-07-02T14:17:54+00:00Oli Scherergithub333195615777966@oli-obk.de2025-03-06T10:51:59+00:00urn:sha1:845d9ff96327bc3c9a8ca07d4f9f275ce09384dfImplement DesugaringKind::FormatLiteral2025-06-22T08:58:25+00:00mejrs59372212+mejrs@users.noreply.github.com2025-06-16T15:51:29+00:00urn:sha1:b1d18129d199c095372c39f75a5c3fb31ea166c2library/compiler: add `PointeeSized` bounds2025-06-16T23:04:33+00:00David Wooddavid.wood2@arm.com2025-02-10T14:18:20+00:00urn:sha1:884d0e031a046af894b43180032c1803bb6d0834
As core uses an extern type (`ptr::VTable`), the default `?Sized` to
`MetaSized` migration isn't sufficient, and some code that previously
accepted `VTable` needs relaxed to continue to accept extern types.
Similarly, the compiler uses many extern types in `rustc_codegen_llvm`
and in the `rustc_middle::ty::List` implementation (`OpaqueListContents`)
some bounds must be relaxed to continue to accept these types.
Unfortunately, due to the current inability to relax `Deref::Target`,
some of the bounds in the standard library are forced to be stricter than
they ideally would be.
`Display`: Rework explanation of `FromStr`/`Display` round-tripping2025-06-03T22:41:47+00:00Josh Triplettjosh@joshtriplett.org2025-06-03T22:39:46+00:00urn:sha1:742014e7e3576f3053e7c63fc930c4d5b5b7a477
- Drop "usually a mistake"
- Add phrasing from `FromStr` about round-tripping, and about how the
inability to round-trip may surprise users.
Improve the documentation of `Display` and `FromStr`, and their interactions2025-06-03T22:41:47+00:00Josh Triplettjosh@joshtriplett.org2025-02-07T13:53:34+00:00urn:sha1:252ad18415723a7485b0e2950f1b641109c9d4ef
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.