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

@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.
"""

https://github.com/rust-lang/rust/issues/127343#issuecomment-2218261296

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

Like 30 July at 3:51 | Open on social.treehouse.systems

2 comments

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 (https://rust-lang.github.io/rfcs/1105-api-evolution.html#minor-change-implementing-any-non-fundamental-trait) but agree it's frustrating :(

30 July at 4:09 | Open on mastodon.boiler.social

c-x-b :verified: :verified:

really dumb nitpickery

@mgorny if I understand correctly this fell out of a change to std (https://github.com/rust-lang/rust/pull/99969 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

30 July at 4:26 | Open on mastodon.boiler.social