https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp 2025-09-08T13:02:25+00:00 2025-09-08T13:02:25+00:00 cyrgani ansgar.w.zielke@gmail.com 2025-09-07T21:20:40+00:00 urn:sha1:edc94e61841506c6957e1ee0ed57a2232fe339c4 2025-08-15T22:13:28+00:00 Jacob Pratt jacob@jhpratt.dev 2025-08-15T22:13:28+00:00 urn:sha1:2b1a288dfc5a2cce12b8c1a2eef22f89d894c094 Implement `#[derive(From)]` Implements the `#[derive(From)]` feature ([tracking issue](https://github.com/rust-lang/rust/issues/144889), [RFC](https://github.com/rust-lang/rfcs/pull/3809)). It allows deriving the `From` impl on structs and tuple structs with exactly one field. Some implementation notes: - I wasn't exactly sure which spans to use in the derive generating code, so I just used `span` everywhere. I don't know if it's the Right Thing To Do. In particular the errors when `#[derive(From)]` is used on a struct with an unsized field are weirdly duplicated. - I had to solve an import stability problem, where if I just added the unstable `macro From` to `core::convert`, previously working code like `use std::convert::From` would suddenly require an unstable feature gate, because rustc would think that you're trying to import the unstable macro. `@petrochenkov` suggested that I add the macro the the core prelude instead. This has worked well, although it only works in edition 2021+. Not sure if I botched the prelude somehow and it should live elsewhere (?). - I had to add `Ty::AstTy`, because the `from` function receives an argument with the type of the single field, and the existing variants of the `Ty` enum couldn't represent an arbitrary type. 2025-08-15T10:06:20+00:00 Jakub Beránek berykubik@gmail.com 2025-08-04T15:24:18+00:00 urn:sha1:e935a155c2078185f0705bb972a38953e770e393 2025-08-15T06:16:30+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-08-15T06:16:30+00:00 urn:sha1:e3a178234d75ee8545b766653643306d0c3f2919 Implement autodiff using intrinsics This PR aims to move autodiff logic to `autodiff` intrinsic. Allowing us to delete a great part of our frontend code and overall, simplify the compilation pipeline of autodiff functions. 2025-08-14T16:30:15+00:00 Marcelo Domínguez dmmarcelo27@gmail.com 2025-08-14T15:27:57+00:00 urn:sha1:250d77e5d72fde69a6406050a3b037635f685378 2025-08-10T23:18:01+00:00 Josh Triplett josh@joshtriplett.org 2025-08-10T23:17:26+00:00 urn:sha1:38df15805ba5be78d70c515f1d585ee6be95e13b When operating on expressions, `cfg_select!` can now handle expressions without braces. (It still requires braces for other things, such as items.) Expand the test coverage and documentation accordingly. 2025-08-02T09:24:24+00:00 Samuel Tardieu sam@rfc1149.net 2025-08-02T09:24:24+00:00 urn:sha1:d082ff4c04c09e855d7ea55e0c9deda05eba46ec Improve formatting of doc code blocks We don't currently apply automatic formatting to doc comment code blocks. As a result, it has built up various idiosyncracies, which make such automatic formatting difficult. Some of those idiosyncracies also make things harder for human readers or other tools. This PR makes a few improvements to doc code formatting, in the hopes of making future automatic formatting easier, as well as in many cases providing net readability improvements. I would suggest reading each commit separately, as each commit contains one class of changes. 2025-07-26T05:02:09+00:00 Josh Triplett josh@joshtriplett.org 2025-07-26T00:35:47+00:00 urn:sha1:715088094c2e2ef31158b4767ceacfba62c8e6ef Because doc code does not get automatically formatted, some doc code has creative placements of comments that automatic formatting can't handle. Reformat those comments to make the resulting code support standard Rust formatting without breaking; this is generally an improvement to readability as well. Some comments are not indented to the prevailing indent, and are instead aligned under some bit of code. Indent them to the prevailing indent, and put spaces *inside* the comments to align them with code. Some comments span several lines of code (which aren't the line the comment is about) and expect alignment. Reformat them into one comment not broken up by unrelated intervening code. Some comments are placed on the same line as an opening brace, placing them effectively inside the subsequent block, such that formatting would typically format them like a line of that block. Move those comments to attach them to what they apply to. Some comments are placed on the same line as a one-line braced block, effectively attaching them to the closing brace, even though they're about the code inside the block. Reformat to make sure the comment will stay on the same line as the code it's commenting. 2025-07-23T12:26:06+00:00 Jonas Platte jplatte+git@posteo.de 2025-07-22T22:13:11+00:00 urn:sha1:8a1b20ed6021d9e871c60e112dbf136699c87fab 2025-07-17T15:42:54+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-07-11T10:20:25+00:00 urn:sha1:250648e871c1e685f09427bd31fd399090f15640 Also make it *only* usable on nightly