diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2025-01-24 08:08:06 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-24 08:08:06 +0100 |
| commit | a3fb2a0572fb89c2cba52817234740a8859b0006 (patch) | |
| tree | 824d24ada25fb249f6f9893a0e563c590ab355f5 /compiler/rustc_codegen_llvm/src/llvm_util.rs | |
| parent | a7922dbb3f78b3486141c317c5f76aa6f023e8d7 (diff) | |
| parent | 6103896b1fc192740e1190dfdba86a781a84b493 (diff) | |
| download | rust-a3fb2a0572fb89c2cba52817234740a8859b0006.tar.gz rust-a3fb2a0572fb89c2cba52817234740a8859b0006.zip | |
Rollup merge of #135489 - RalfJung:TryFromSliceError, r=tgross35
remove pointless allowed_through_unstable_modules on TryFromSliceError This got added in https://github.com/rust-lang/rust/pull/132482 but the PR does not explain why. `@lukas-code` do you still remember? Also Cc `@Noratrieb` as reviewer of that PR. If I understand the issue description correctly, all paths under which this type is exported are stable now: `core::array::TryFromSliceError` and `std::array::TryFromSliceError`. If that is the case, we shouldn't have the attribute; it's a terrible hack that should only be used when needed to maintain backward compatibility. Getting some historic information right is IMO *not* sufficient justification to risk accidentally exposing this type via more unstable paths today or in the future.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm_util.rs')
0 files changed, 0 insertions, 0 deletions