<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/compiler/rustc_expand/Cargo.toml, branch cargo_update</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=cargo_update</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=cargo_update'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-09-02T09:12:54+00:00</updated>
<entry>
<title>Revert introduction of `[workspace.dependencies]`.</title>
<updated>2025-09-02T09:12:54+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-09-02T09:09:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=301655eafe56a4b5064adebd412becf94b59221c'/>
<id>urn:sha1:301655eafe56a4b5064adebd412becf94b59221c</id>
<content type='text'>
This was done in #145740 and #145947. It is causing problems for people
using r-a on anything that uses the rustc-dev rustup package, e.g. Miri,
clippy.

This repository has lots of submodules and subtrees and various
different projects are carved out of pieces of it. It seems like
`[workspace.dependencies]` will just be more trouble than it's worth.
</content>
</entry>
<entry>
<title>Add `tracing` to `[workspace.dependencies]`.</title>
<updated>2025-08-27T04:21:19+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-08-22T00:39:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c50d2cc8078280a0dfdd562c7688e81b664e5880'/>
<id>urn:sha1:c50d2cc8078280a0dfdd562c7688e81b664e5880</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add `thin-vec` to newly added `[workspace.dependencies]`.</title>
<updated>2025-08-27T03:59:32+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-08-21T21:04:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=777e2d6a2aa92be8f966c147b0d5c96930873807'/>
<id>urn:sha1:777e2d6a2aa92be8f966c147b0d5c96930873807</id>
<content type='text'>
</content>
</entry>
<entry>
<title>remove rustc_attr_data_structures</title>
<updated>2025-07-31T12:19:27+00:00</updated>
<author>
<name>Jana Dönszelmann</name>
<email>jana@donsz.nl</email>
</author>
<published>2025-07-31T09:00:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e1d3ad89c7a2ad4f5d944a7fee1298ffe8c99645'/>
<id>urn:sha1:e1d3ad89c7a2ad4f5d944a7fee1298ffe8c99645</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not get proc_macro from the sysroot in rustc</title>
<updated>2025-05-27T15:49:28+00:00</updated>
<author>
<name>bjorn3</name>
<email>17426603+bjorn3@users.noreply.github.com</email>
</author>
<published>2025-05-27T10:30:47+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=026baa1c6fb397e9bd2c171d750c939232c13a58'/>
<id>urn:sha1:026baa1c6fb397e9bd2c171d750c939232c13a58</id>
<content type='text'>
With the stage0 refactor the proc_macro version found in the sysroot
will no longer always match the proc_macro version that proc-macros get
compiled with by the rustc executable that uses this proc_macro. This
will cause problems as soon as the ABI of the bridge gets changed to
implement new features or change the way existing features work.

To fix this, this commit changes rustc crates to depend directly on the
local version of proc_macro which will also be used in the sysroot that
rustc will build.
</content>
</entry>
<entry>
<title>Remove rustc_attr_data_structures re-export from rustc_attr_parsing</title>
<updated>2025-05-18T16:14:43+00:00</updated>
<author>
<name>mejrs</name>
<email>59372212+mejrs@users.noreply.github.com</email>
</author>
<published>2025-05-18T16:14:43+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=178e09ed3705ee7eed64cfecb02173e9f54d82b0'/>
<id>urn:sha1:178e09ed3705ee7eed64cfecb02173e9f54d82b0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "Use workspace lints for crates in `compiler/` #138084"</title>
<updated>2025-03-10T10:12:47+00:00</updated>
<author>
<name>许杰友 Jieyou Xu (Joe)</name>
<email>39484203+jieyouxu@users.noreply.github.com</email>
</author>
<published>2025-03-10T10:12:34+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=063ef18fdc10cb0eb49e1af855e1a8e807e73eed'/>
<id>urn:sha1:063ef18fdc10cb0eb49e1af855e1a8e807e73eed</id>
<content type='text'>
Revert &lt;https://github.com/rust-lang/rust/pull/138084&gt; to buy time to
consider options that avoids breaking downstream usages of cargo on
distributed `rustc-src` artifacts, where such cargo invocations fail due
to inability to inherit `lints` from workspace root manifest's
`workspace.lints` (this is only valid for the source rust-lang/rust
workspace, but not really the distributed `rustc-src` artifacts).

This breakage was reported in
&lt;https://github.com/rust-lang/rust/issues/138304&gt;.

This reverts commit 48caf81484b50dca5a5cebb614899a3df81ca898, reversing
changes made to c6662879b27f5161e95f39395e3c9513a7b97028.
</content>
</entry>
<entry>
<title>Specify rust lints for `compiler/` crates via Cargo.</title>
<updated>2025-03-07T21:41:09+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-03-06T00:53:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=beba32cebb4fb2ef8f02c4fc898a9d31f1b03c61'/>
<id>urn:sha1:beba32cebb4fb2ef8f02c4fc898a9d31f1b03c61</id>
<content type='text'>
By naming them in `[workspace.lints.rust]` in the top-level
`Cargo.toml`, and then making all `compiler/` crates inherit them with
`[lints] workspace = true`. (I omitted `rustc_codegen_{cranelift,gcc}`,
because they're a bit different.)

The advantages of this over the current approach:
- It uses a standard Cargo feature, rather than special handling in
  bootstrap. So, easier to understand, and less likely to get
  accidentally broken in the future.
- It works for proc macro crates.

It's a shame it doesn't work for rustc-specific lints, as the comments
explain.
</content>
</entry>
<entry>
<title>Introduce new-style attribute parsers for several attributes</title>
<updated>2025-02-24T13:31:17+00:00</updated>
<author>
<name>Jana Dönszelmann</name>
<email>jana@donsz.nl</email>
</author>
<published>2025-02-09T21:49:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=7e0f5b50168c63bd1879067c043559ef0f01671e'/>
<id>urn:sha1:7e0f5b50168c63bd1879067c043559ef0f01671e</id>
<content type='text'>
note: compiler compiles but librustdoc and clippy don't
</content>
</entry>
<entry>
<title>Upgrade the compiler to edition 2024</title>
<updated>2025-02-22T00:01:48+00:00</updated>
<author>
<name>Michael Goulet</name>
<email>michael@errs.io</email>
</author>
<published>2025-02-20T18:37:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=76d341fa09c423e601e2c47f8e4d165fcb7c21aa'/>
<id>urn:sha1:76d341fa09c423e601e2c47f8e4d165fcb7c21aa</id>
<content type='text'>
</content>
</entry>
</feed>
