# Rust 1.66.0 pre-release testing **URL:** \ **Category:** announcements\ **Created:** [December 12, 2022, 9:02pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966 "2022-12-12T21:02:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\ **Post date:** [December 12, 2022, 9:02pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/1 "2022-12-12T21:02:07Z")
The 1.66.0 pre-release is ready for testing. The release is scheduled for December 15. [Release notes can be found here.](https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1660-2022-12-15) You can try it out locally by running: ```nohighlight RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable ``` The index is [https://dev-static.rust-lang.org/dist/2022-12-12/index.html](https://dev-static.rust-lang.org/dist/2022-12-12/index.html). The release team is also thinking about changes to our pre-release process: we'd love your feedback [on this GitHub issue](https://github.com/rust-lang/release-team/issues/16). ---
**Author:** ![PoignardAzur](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/poignardazur/32/6464_2.png) [@PoignardAzur](https://internals.rust-lang.org/u/PoignardAzur)\ **Post date:** [December 13, 2022, 8:15am UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/2 "2022-12-13T08:15:06Z")
Small changes this time around. It's quite a contrast with the last release! ---
**Author:** ![tronta](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/tronta/32/10275_2.png) [@tronta](https://internals.rust-lang.org/u/tronta)\ **Post date:** [December 13, 2022, 4:43pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/3 "2022-12-13T16:43:01Z")
There are some things not quite correct: - ..X is not yet stable (I have created a PR for that: [Remove ..X from RELEASES.md by tronta · Pull Request #105658 · rust-lang/rust · GitHub](https://github.com/rust-lang/rust/pull/105658) - The link behind [`std::os::fd`](https://doc.rust-lang.org/stable/std/os/fd/index.html), does not work ---
**Author:** ![cuviper](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cuviper/32/1897_2.png) [@cuviper](https://internals.rust-lang.org/u/cuviper)\ **Post date:** [December 13, 2022, 5:29pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/4 "2022-12-13T17:29:20Z")
The link works if you change `/stable/` to `/beta/`, so that will go live after the actual release. ---
**Author:** ![tronta](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/tronta/32/10275_2.png) [@tronta](https://internals.rust-lang.org/u/tronta)\ **Post date:** [December 13, 2022, 5:58pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/5 "2022-12-13T17:58:56Z")
Thanks, ---
**Author:** ![seancross](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@seancross](https://internals.rust-lang.org/u/seancross)\ **Post date:** [December 15, 2022, 6:35am UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/6 "2022-12-15T06:35:48Z")
It seems as though `rust-lld` with `lto="fat"` is not working. I discovered the issue with `riscv32imac-unknown-xous-elf`, and was able to replicate it with `x86_64-fortanix-unknown-sgx`: [rust-lld: lto="fat" no longer works](https://github.com/rust-lang/rust/issues/105734) ---
**Author:** ![kpreid](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/kpreid/32/8484_2.png) [@kpreid](https://internals.rust-lang.org/u/kpreid)\ **Post date:** [December 15, 2022, 5:59pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/7 "2022-12-15T17:59:19Z")
We aren't in the pre-release period any more, but this is arguably a “release documentation” problem more than a bug, so I thought I'd mention it here: the changelog for Clippy says that `uninlined_format_args` is new and enabled by default, but it isn't enabled by default. > > > \### Summary > > \[The changelog linked from Rust 1.66 release notes\](https://githu…b.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-166) says that the lint \`uninlined\_format\_args\` was added in Rust 1.66. Following the link from there to \[the lint list\](https://rust-lang.github.io/rust-clippy/master/index.html#uninlined\_format\_args) says that the lint is in the \`style\` group and warn by default. However, this does not seem to be the case \_in the stable release\_; it does not warn unless set explicitly. > > \### Lint Name > > uninlined\_format\_args > > \### Reproducer > > I tried this code: > > \`\`\`rust > pub fn foo(x: &str) -\> String { > format!("Foo {}", x) > } > \`\`\` > > I expected to see this happen: A \`uninlined\_format\_args\` warning. > > Instead, this happened: No warnings, unless I add \`#\[warn(clippy::uninlined\_format\_args)\]\`. > > Adding \`#\[warn(clippy::style)\]\` also has no effect even though the lint claims to be part of the \`style\` group. > > \### Version > > \`\`\`text > rustc 1.66.0 (69f9c33d7 2022-12-12) > binary: rustc > commit-hash: 69f9c33d71c871fc16ac445211281c6e7a340943 > commit-date: 2022-12-12 > host: x86\_64-apple-darwin > release: 1.66.0 > LLVM version: 15.0.2 > \`\`\` > > Note: This does not reproduce in nightly, including via Rust Playground —— the lint triggers as expected — suggesting that the problem is that the change to make this lint part of the \`style\` group missed being included in the stable release even though the changelog claims it did. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\ **Post date:** [March 15, 2023, 6:00pm UTC](https://internals.rust-lang.org/t/rust-1-66-0-pre-release-testing/17966/8 "2023-03-15T18:00:06Z")
Closed on March 15, 2023, 6:00pm UTC This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.