![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
On top of that they’re still paying using their time (and power).
On top of that they’re still paying using their time (and power).
I’m sure the image posted doesn’t have an exploded charger that could indicate why the comment you replied to was made!
It shouldn’t be lol
Sometimes you do, you don’t stop being a parent after your child turns 18. You can still try and help them especially if you think something this simple has been done wrong. Shaming your child online because of how they load the dishwasher is just stupid.
Then you’re probably teaching wrong.
You didn’t answer the question or have interest in pursuing a conversation about the topic at hand.
This would generally very quickly stop being a casual conversation saying stuff like that, there’s no point to it. Most of us get it, we’re not here to be reminded.
three paragraphs and yet you didn’t say anything lol
Not to mention a lot of massive companies also use it at every part of the stack, Rust is good at it all and it is beautifully and perfectly suited for tasks like these.
Exactly! The other wrapper enum I named (Option) is the same kind of concept but with Some(value)
and None
.
Here’s some examples written on my phone:
match result {
Ok(bool_name) => whatever,
Err(error_type) => whatever,
}
if let Ok(bool_name) = result {
whatever
}
if result.is_ok() {
whatever
}
let whatever = result.unwrap_or_default();
let whatever = result?;
And there’s many other awesome ways to use a Result including turning it into an Option or unwrapping it unsafely. I recommend you just search “Rust book” on your search engine and browse it. Here’s the docs to the Result enum.
It’s a great and probably the best error system I’ve seen, instead of just throwing errors and having bulky try catch statements and such there’s just a result type.
Say you have a function that returns a boolean in which something could error, the function would return a Result<bool, Error> and that’s it. Calling the function you can choose to do anything you want with that possible Error, including ignoring it or logging or anything you could want.
It’s extremely simple.
You don’t with Rust either.
That’s where the keyword imagine comes in.
deleted by creator
This is genuinely my worst fear and I hate this statement.
That’s exactly what I was missing: giant distracting icons that flash on a comment I was going to read anyways!
What you’re doing isn’t productive.
I’m sorry to tell you this so hastily but everyone else is a bot, it is just you and everything you’ve experienced is completely unique to you.
They’ve very much revealed that they come straight from 4chan.