banning patients

Did you mean patents?

I can agree that the example function is not the best usecase. But the point still stand that there’s no realistic escape hatch from lifetimes and memory management in Rust.

Cow does not work when you are actually required to return a reference, e.g. if you’re working with some other crate that requires that. Cow also has some more strict requirements on reborrows (i.e. you can reborrow a &'short &'long T to a &'long T, but you can only reborrow a &'short Cow<'long, T> to a &'short T).

LazyLock can solve very specific issues like static, but is not a general escape hatch. Again, the example is not the best to showcase this, but imagine if you have to perform this operation for an unknown amount of runtime values. LazyLock will only work for the very first one.

(Note that I’m not the article author)

In this example, you could have just made a constant with value 0 and returned a reference to that. It would also have a 'static lifetime and there would be no leaking.

I believe the intention was to demonstrate something that works with runtime values too, and a constant 0 does not.

Btw you can just write &0 to do what you proposed, there’s no need for an explicit constant/static.

compile rust 0.7 in scala

Not sure if there was another rewrite, but AFAIK (and the article agrees with me) rustc was originally written in Ocaml

Where’s the punch?

In the face of everyone expecting an upgrade

Gnome 47 will have support for accent colors if that’s what you want.

Does GNOME really need an app to change the theme?

You can also do what this app does manually. The point is that “themes” are an hack and not officially supported, as such it doesn’t make sense to provide an official interface to set them.

KDE plasma has this natively…

Do you mean for global themes, application styles or plasma styles? All application styles I can find either use Kvantum or require you to compile them manually…

Software implementations of those features is often slower, and runtime checking can often be too expensive compared to the gains.

since it seems like nobody but cachy or custom kernel runs anything but V1

Gentoo offers x86_64-v4 binary builds too.

There was a proposal for Fedora too, though it was ultimately rejected.

Ultimately the gains right now seem to be only 1-3%, though that might also be because there’s not much demand for these kind of optimizations. If more distros enable them they might become more widespread and the benefits might increase too. It’s a chicken-egg problem though.

Emails are nowhere near being competitive with discord. Sure, they’re technically more accessible, but in practice they are much less usable by random people which in turn will just avoid interacting or contributing with your project.

To be fair trees still use energy for doing this, but that energy is conveniently provided by the sun.

High or low level doesn’t matter. Mathematically it just makes more sense to use 0-based indexing https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html

It’s mentioned in footnote 6:

As an example, to make this work I’m assuming some kind of “true deref” trait that indicates that Deref yields a reference that remains valid even as the value being deref’d moves from place to place. We need a trait much like this for other reasons too.

It would only work for references that are stable after the value they reference is moved. Think for example of a &str you get from a String.

Can’t those be installed in toolbox?

Metro UI toggle buttons were rectangular though.

GNOME devs never said that theming is incompatible (just “not supported”), and you’re still not explaining whay you mean with “incompatible” either. Managing window controls also doesn’t seem a requirement to be “compatible”, as the app still runs fine even with client side decorations (again, it just won’t fit visually with the rest of the system).

And by the way, the problem is not theming per-se, but the fact that apps get themed by default, they inevitably break by default, and app developers are left to deal with that. Nobody ever tried to improve the situation so the solution they came up with is to have their apps always look the same.

How about when the theming is baked in and impossible to change?

It can still be changed, it’s just a harder to do so.

It’s about doing things that go against the interests of the user.

This conveniently ignores that app developers are also users of ui frameworks, and they would like a well defined platform to test for, rather than an endless stream of distros each with its own theme that could break their app.

Libadwaita is only compatible with gnome and only works with gnome. Other DE’s can try to make it work in their DE, but the experience for them is hostile.

Not sure what you mean with “compatible”, as libadwaita apps are supposed to work on other DEs as well. It might not fit visually with them, but that’s not being incompatible.

They tested the same strings on that implementation

The code they were looking at was used for writing the table, but they were testing the one that read it (which is instead correct).

though judging by the recent comments someone’s found something.

Yeah that’s me :)The translation using an associated const also works when the const block uses generic parameters. For example:

fn require_zst() {
    const { assert!(std::mem::size_of::() == 0) }
}

This can be written as:

fn require_zst() {
    struct Foo(PhantomData);
    impl Foo {
        const FOO: () = assert!(std::mem::size_of::() == 0);
    }
    Foo::::FOO
}

However it cannot be written as:

fn require_zst() {
    const FOO: () = assert!(std::mem::size_of::() == 0);
    FOO
}

Because const FOO: () is an item, thus it is only lexically scoped (i.e. visible) inside require_zst, but does not inherit its generics (thus it cannot use T).

They tested the same strings on that implementation

The strings were the same, but not the implementation. They were testing the decoding of the strings, but the C function they were looking at was the one for encoding them. The decoding function was correct but what it read didn’t match the encoding one.

though judging by the recent comments someone’s found something.

Yeah, that’s me :)

while a similar C implementation does not need this fix

No, that implementation also needs the fix. It’s just that it was never properly tested, so they thought it was working correctly.