What changed in Go, Rust and Solidity this week.

Testing in Go often needs a way to print messages that are tied to the test’s output stream. The testing package already provides t.Log and t.Logf, but those helpers add source‑location information and newlines automatically. A new method, Output, was proposed for the testing.TB interface. It returns an io.Writer that writes to the same stream as t.Log, but it does not add caller information or newlines. The writer is line‑buffered and flushes when the test ends. After a test finishes, calling Output or writing to it panics.

The target i686-pc-windows-gnu is a 32‑bit Windows build that uses the GNU toolchain. It was previously classified as a Tier 1 target, meaning it receives the same level of maintenance and testing as the most popular platforms. The change moves it to Tier 2, which is a lower priority for maintenance. This means that if you build for this target you may see fewer updates and less support compared to other Tier 1 targets.

Rustup 1.28.1 is a new release of the Rust toolchain installer. It brings a few small improvements and bug fixes, but nothing that changes how you write Rust code. The update is only relevant if you use rustup to manage your toolchains.

Rust lets you write types that depend on a constant value, like an array size. Before this change you always had to write that constant explicitly, even if the compiler could figure it out. The new feature will let the compiler guess the constant for you, so you can omit it in many places. The announcement is a call for people to try it out and report any problems.

The Rust team fixed a typo in the name of an RFC file and updated the link to the pull request that introduced the change. This is a housekeeping update, not a language feature. It does not affect any Rust code you write.

The RFC 2093 about *infer‑outlives* had a small spelling mistake. The change simply corrected that typo. Nothing in the language itself was altered, so the code you write today behaves exactly as before.

The RFC 3771 document had the wrong start date. A start date tells the Rust team when a change should become official. The correction simply updates that date to the right value. No code or compiler behavior changes.

The Rust team posted a note about changes to their test infrastructure for January and February 2025. The note is a brief announcement and does not describe any new language feature or library change. It simply informs the community that the test infrastructure has been updated.