They aren't shown to users, no, but because votes are federated, they're freely accessible to anyone willing to put in some effort. Set up a server and you'll get access to the data.
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.
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.
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:
rust
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:
rust
// 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:
rust
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`
Mark With a Z @ sevon @lemmy.kde.social Posts 4Comments 114Joined 1 yr. ago
They aren't shown to users, no, but because votes are federated, they're freely accessible to anyone willing to put in some effort. Set up a server and you'll get access to the data.