Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.38] Regression: failed to resolve: use of undeclared type or module SliceConcatExt #63892

Closed
petrochenkov opened this issue Aug 25, 2019 · 3 comments
Labels
regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Milestone

Comments

@petrochenkov
Copy link
Contributor

#63628 (comment)

failed to resolve: use of undeclared type or module SliceConcatExt

./gh/echupriyanov/tls-ws/beta-2019-08-13.txt:[INFO] [stderr] error[E0433]: failed to resolve: use of undeclared type or module `SliceConcatExt`

SliceConcatExt was an unstable standard library trait removed in #62403.

@petrochenkov petrochenkov added regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Aug 25, 2019
@Mark-Simulacrum Mark-Simulacrum added this to the 1.38 milestone Aug 30, 2019
@Mark-Simulacrum
Copy link
Member

Closing as expected breakage (cc @rust-lang/libs, but this is so minimally breaking and was an unstable use).

@SimonSapin
Copy link
Contributor

Ouch, it turns out an unstable trait in the prelude can be named without any #![feature(…)] opt-in.

https://github.com/echupriyanov/tls-ws/blob/d458e2edfabc7e28494482987afbb5eebba1de7f/src/bin/server.rs#L117 reduced:

fn main() {
    dbg!(SliceConcatExt::join(&["foo", "bar"][..], "-"));
}

Not to say that we should revert or do anything else here, but to keep in mind next time we consider adding an unstable trait in the prelude. Or should we consider that a compiler bug?

@Mark-Simulacrum
Copy link
Member

Yeah, looks like a compiler bug (probably similar to the other stability problems with 'absolute' paths -- if we're importing it for you it probably bypasses stability by looking like a root path?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants