@WG-prioritization/alerts issue #82151 has been requested for prioritization.
Linking error on valid code, symbols not exported. Looks like a
P-high, but goes to at least beginning 2018.
hmm probably I would also say
P-high as the previous linked issue.
I am missinf @Hameer Abbasi where you find a reference so back in time. At a cursory look, the linked issue go back up to mid 2019 with stable 1.36 (though I admit I got a bit lost exploring the linked issues).
I am asking to understand if this can be considered a stable-to-stable regression (which I tend to say yes)
cargo-bisect-rustc with a start date set to
@WG-prioritization I am re-reading this issue and I agree with Hameer Abbasi on a high priority, but I am also wondering about the impact, if this issue is really there since so long. The issue seems to be about working code not working anymore after updating dependencies.
Which team could be pinged to have a look at that?
To clarify: crates compile and test fine on both old and new versions. But externally, the linker doesn’t find symbols even though there’s a
pub and a
pub use. Is there a linking or exporting symbols team? 🙂
It may just be that the crate, when updated, introduced the bug. The question is, should
pub use re-export symbols?
I think t-compiler is fine. I don't have the context for more reasoning about this issue.
I'm asking myself the question if this needs to be pushed on the agenda table with an
by the way, could you add the results of your bisection? they could add interesting data
Added the results about the bisection, I agree with
Brief discussion during the meeting.
Let's leave it
I-nominate for discussion in 2 weeks (March, 11th) and assign
Issue #82151's prioritization request has been removed.