It’s not copyright infringement if you’re as big as meta.

If you go with something that isn’t lemmy/piefed/mbin, you should look into compatibility and project activity very carefully.

I think the color had just shown up. It’s been a while, I don’t remember specifics that well. The movie was great though and the encounter was so funny we didn’t mind it.

I watched this in theater. It was very late and there was only one other group of people. During the film one of them loudly said something like “what the fuck is this shit” and they walked out pretty early.

I guess it’s not for everyone.

Classic, but I’m more of a Con Air man myself

You’re god damn right with that opinion

Oh boy, now I can stop missing C++

You’d have a hard time finding a company that would just give you access to a vps or managed instance for free. Running a server always costs someone money.

Not very likely. Translating cpu architectures is completely different from from what wine/proton does. A compatibility layer for arm would be even more difficult and expensive, and have a performance penalty. They might plan that for further into future though, if arm pcs take off. A Mac implementation would probably need a lot of apple-specific work, and there aren’t many mac gamers out there.

I know, but it does let you sled off a cliff if you choose to.

Oh boy, not this bullshit again

Prefix the name with what it’s for. For example, I’ve previously got a SoundFontError from opening soundfont file.

“Error” is already used by std::error::Error. It might not be imported by the code that imports your error type, but I think it’s better to give it distinct name.

The other thing is that you might want to use more than one library. Typical imports at the top of the file might look like this:

use bingbong::{BingBong, BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, CrotchidizerError};

If both libraries named their error enums just “Error”, the collision could be worked around, but it’s an unnecessary extra step:

// Not sure how renaming affects compiler hints.
use bingbong::{BingBong, Error as BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, Error as CrotchidizerError};

or if you want to avoid renaming:

use bingbong::{BingBong, SomethingElse};
use bogos::binted::crotchidizer::{self, Crotchidizer};

/* ... */

    match result {
        Ok(value) => return value,
        Err(bingbong::Error::MissionFailed) => panic!(),
        Err(bingbong::Error::UrMom) => todo!(),
        _ => unreachable!(),
    }
    
    if let Err(crotchidizer::Error::SomethingsWrong) = result2 {
        // ...
    }
    

If the screenshot had followed conventions, the message would say something like this:

could not convert error type `BingBongError` to `MyAppError`

You can wrap everything in unsafe and keep living dangerously!

ZBOOBS

I don’t know if this will be attempt, but I helped. Godspeed, OP

They did? I still have it enabled and it works. If I get an update that removes this, mozilla can go shit themselves

Every charger I have lying around charges every device I have lying around. I’m happy with that.

You really should avoid naming your type plain “Error”

This inspired me to look up mozilla graveyard, and yeah, it exists

https://killedbymozilla.com/

Thanks, I hate it.