Email or username:

Password:

Forgot your password?
Michał's posts Post Back to profile
Michał Górny

I can't bump #uv in #Gentoo again, because it — once again — switched to requiring the very newest #RustLang compiler, released not even a week ago. Of course, the new release of the compiler breaks some crates. Of course, since everything is pinned in Rust, we now have to go through tremendous effort patching stuff before we'll be able to get the new version in.

But no, Rust is going great. Also, don't forget that it's Python breaking backwards compatibility all the time.

Also, this is why gccrs will never work. What's the advantage of having an alternative compiler when it will need to catch up with the reference implementation within days of release?

github.com/gentoo/gentoo/pull/

30 July at 2:44 | Open on social.treehouse.systems
19 comments
Howard Chu @ Symas

@mgorny rust implementors are unserious

30 July at 3:11 | Open on mastodon.social
ionizedGirl

@mgorny I don't understand the motivation for shipping pins

30 July at 3:15 | Open on toot.cat
Michał Górny

@ionizedgirl, because new versions break everything all the time!

30 July at 3:24 | Open on social.treehouse.systems
ionizedGirl

@mgorny but there's already a version in the in the cargo.toml 😭

30 July at 3:25 | Open on toot.cat
feld
@mgorny won't take language seriously until it acts like an adult
30 July at 3:41 | Open on bikeshed.party
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?

30 July at 3:43 | Open on mastodon.boiler.social
c-x-b :verified: :verified:
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

30 July at 3:51 | Open on social.treehouse.systems
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 :(

30 July at 4:09 | Open on mastodon.boiler.social
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

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

@mgorny

Rust breaking Mozilla stuff is the reason I didn't bump it yet. But at least for this direction there is rustup.

"Every laguage ecosystem repeats every error of their predecessors"

#uv #Gentoo #RustLang #issuecomment

30 July at 5:38 | Open on chaos.social
Molly

@mgorny Are they always using the newest features or are the requiring the newest compiler just because? If the later, maybe they can be persuaded to give it a bit of time?

30 July at 6:44 | Open on toot.kif.rocks
Andreas Grois

@mgorny Crates tracking the latest toolchain is a major annoyance - also for Rust devs that don't develop for PC and are stuck with whatever rustc version the SDK for their target offers. One of my projects is probably still stuck with Rust 1.52...

Imho rustup was a mistake.

30 July at 7:12 | Open on mastodon.gamedev.place
Go Up