Email or username:

Password:

Forgot your password?
Top-level
c-x-b :verified: :verified:

@mgorny

Of course, the new release of the compiler breaks some crates.

wait, what? I thought rustc had some pretty serious regression testing to catch these things?

4 comments
Michał Górny

@cxberger, it gets even better. They've literally handwaved the issue:

"""
We discussed this regression in today's rust-lang/libs-api team meeting, and agree there's nothing to change on Rust's end. Those repos that have an old version of time in a lockfile will need to update that.
"""

github.com/rust-lang/rust/issu

So yeah, they knew prior to the release, and they've done it anyway.

@cxberger, it gets even better. They've literally handwaved the issue:

"""
We discussed this regression in today's rust-lang/libs-api team meeting, and agree there's nothing to change on Rust's end. Those repos that have an old version of time in a lockfile will need to update that.
"""

github.com/rust-lang/rust/issu

c-x-b :verified: :verified:

@mgorny yeah, i saw that. i did a little more poking about and i guess this is the Stated Policy, Actually (rust-lang.github.io/rfcs/1105-) but agree it's frustrating :(

c-x-b :verified: :verified:

@mgorny if I understand correctly this fell out of a change to std (github.com/rust-lang/rust/pull added trait impls to Box<str>, through normal you-can-write-it-yourself-no-intrinsics-here code) which I think gccrs wouldn't choke on (assuming gccrs has traits basically correct, anyway.)

idk I'm not a language author, just an end user who ~never sees these things. Python (since everyone worth dealing with moved to 3.x) doesn't feel better/worse from here so maybe I'm just a dumbass

Go Up