rust/compiler/rustc_serialize/src, branch 1.84.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.84.12024-10-16T13:44:16+00:00Fix explicit_iter_loop in rustc_serialize2024-10-16T13:44:16+00:00Michal Piotrowskipracticalrs.com@gmail.com2024-10-16T13:44:16+00:00urn:sha1:b2b4ad4cc94077eba1331acc534b5e36ae3e2603Stabilize `const_option`2024-10-12T21:07:13+00:00Trevor Grosstmgross@umich.edu2024-10-01T21:11:48+00:00urn:sha1:19f6c17df486c5f70c1000ecada39c62b9c93550
This makes the following API stable in const contexts:
impl<T> Option<T> {
pub const fn as_mut(&mut self) -> Option<&mut T>;
pub const fn expect(self, msg: &str) -> T;
pub const fn unwrap(self) -> T;
pub const unsafe fn unwrap_unchecked(self) -> T;
pub const fn take(&mut self) -> Option<T>;
pub const fn replace(&mut self, value: T) -> Option<T>;
}
impl<T> Option<&T> {
pub const fn copied(self) -> Option<T>
where T: Copy;
}
impl<T> Option<&mut T> {
pub const fn copied(self) -> Option<T>
where T: Copy;
}
impl<T, E> Option<Result<T, E>> {
pub const fn transpose(self) -> Result<Option<T>, E>
}
impl<T> Option<Option<T>> {
pub const fn flatten(self) -> Option<T>;
}
The following functions make use of the unstable
`const_precise_live_drops` feature:
- `expect`
- `unwrap`
- `unwrap_unchecked`
- `transpose`
- `flatten`
Fixes: <https://github.com/rust-lang/rust/issues/67441>
Fix needless_lifetimes in rustc_serialize2024-10-08T13:17:45+00:00Michal Piotrowskipracticalrs.com@gmail.com2024-10-08T13:17:45+00:00urn:sha1:7ab466697faf64aaeda40d6407c01f6bfff83fdbFix used_underscore_binding in rustc_serialize2024-10-07T13:02:45+00:00Michal Piotrowskipracticalrs.com@gmail.com2024-10-07T13:02:45+00:00urn:sha1:4085b48dfddd742fa4d46c594ee5662b972ae6deAuto merge of #129777 - nnethercote:unreachable_pub-4, r=Urgau2024-09-03T01:27:20+00:00borsbors@rust-lang.org2024-09-03T01:27:20+00:00urn:sha1:6199b69c53a8c275ca3cd59647ea0af5ca29aae2
Add `unreachable_pub`, round 4
A follow-up to #129732.
r? `@Urgau`
Add `warn(unreachable_pub)` to `rustc_serialize`.2024-09-02T22:49:54+00:00Nicholas Nethercoten.nethercote@gmail.com2024-08-30T00:45:32+00:00urn:sha1:21a37da26840ae34a02246ea9141b28efd6e8ce5chore: Fix typos in 'compiler' (batch 2)2024-09-02T05:50:22+00:00Alexander Cyonalex.cyon@gmail.com2024-09-02T05:50:22+00:00urn:sha1:00de006f22f2304bddabb2d00a13af242ea21c17Reformat `use` declarations.2024-07-28T22:26:52+00:00Nicholas Nethercoten.nethercote@gmail.com2024-07-28T22:13:50+00:00urn:sha1:84ac80f1921afc243d71fd0caaa4f2838c294102
The previous commit updated `rustfmt.toml` appropriately. This commit is
the outcome of running `x fmt --all` with the new formatting options.
chore: remove duplicate words2024-07-02T03:25:31+00:00hattizaihattizai@gmail.com2024-07-02T03:25:31+00:00urn:sha1:ada9fda7c38b1be39b4e8273ee6af150985df064Use `tidy` to sort crate attributes for all compiler crates.2024-06-12T05:49:10+00:00Nicholas Nethercoten.nethercote@gmail.com2024-06-12T03:49:36+00:00urn:sha1:75b164d836ff82b459dfb05646bf0328dd23d2fd
We already do this for a number of crates, e.g. `rustc_middle`,
`rustc_span`, `rustc_metadata`, `rustc_span`, `rustc_errors`.
For the ones we don't, in many cases the attributes are a mess.
- There is no consistency about order of attribute kinds (e.g.
`allow`/`deny`/`feature`).
- Within attribute kind groups (e.g. the `feature` attributes),
sometimes the order is alphabetical, and sometimes there is no
particular order.
- Sometimes the attributes of a particular kind aren't even grouped
all together, e.g. there might be a `feature`, then an `allow`, then
another `feature`.
This commit extends the existing sorting to all compiler crates,
increasing consistency. If any new attribute line is added there is now
only one place it can go -- no need for arbitrary decisions.
Exceptions:
- `rustc_log`, `rustc_next_trait_solver` and `rustc_type_ir_macros`,
because they have no crate attributes.
- `rustc_codegen_gcc`, because it's quasi-external to rustc (e.g. it's
ignored in `rustfmt.toml`).