adotinthevoid

RE: @rustnl@fosstodon.org

come see my talk! people are already calling it “one of the talks that will be delivered at RustWeek 2026 in Utrecht this May 18-23”

RE: @adotinthevoid@hachyderm.io

Here it is: https://alona.page/talks/freeing-rustcs-understanding.pdf

(Slides only, no recordings)

My talk's gonna be soo good.

(Tomorrow, in Cambridge UK: https://www.meetup.com/cambridge-rust-meetup/events/312749221/)

https://www.gov.uk/guidance/style-guide/technical-content-a-to-z#breaking-changes

the UK government has an official position that breaking changes are not broadly understood.

longest requested rustdoc-json feature (i think?) has a very WIP implementation: https://github.com/rust-lang/rust/pull/149043

observation: Rustdoc as the start of a sentence seems fine. Rustc on the other hand seems viscerally wrong. rustc is the only way to capitalize that. rustdoc is also acceptable here, but not required.

rust's ir's are soo goofy sometimes:

In the AST a generic bound can either exist on the definition (`fn foo<T: Debug>()`) or (`fn foo<T>() where T: Debug`).

Then in AST->HIR, this is de-sugared/normalized, and all bounds are moved to where clauses (so it's easier for the typechecker to look at all the bounds)

Then in HIR->rustdoc::clean, this is reversed back to how it was in the AST. The bounds are split back into those on the param-defs, and those in where clauses. (So rustdoc can show the code as users wrote it).

This structure is repeated in rustdoc-json output, which bounds both on param defs and where clauses.

Then rustdoc-json consumers like cargo-semver-checks redo the same normalization again, for the same reasons.

https://github.com/rust-lang/rustc-dev-guide/pull/2422 Finally documented the rustdoc-json test suites after literal years of having this as a todo!

holy moly, hash_map! macro in std?!??!! https://github.com/rust-lang/libs-team/issues/578#issuecomment-3074413211

rustdoc-json finally has structured attributes, using an enum rather than a string. This sould mean no more parsing by consumers, and `FORMAT_VERSION` breaking due to rustc refactoring: https://github.com/rust-lang/rustdoc-types/blob/trunk/CHANGELOG.md#v0.54.0

@NathanielB@types.pl was it you?