In Rust, using the Option and Result types make the general flow of the application much easier to organize, make modular, and reuse.
In Rust, using the Option and Result types make the general flow of the application much easier to organize, make modular, and reuse.
This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: “Both of these functions check the same thing, but parseNonEmpty
gives the caller access to the information it learned, while validateNonEmpty
just throws it away.”
In what scenario could the first character be a newline character? I think that if-statement may be unnecessary, but I never use raw user input like you are here.
I’m not sure that you need a range when pulling the character from the input
variable. Simply input[i]
and input[input.len() - i - 1]
should work.
Boo, just missed it.
Is this already in a crate? I’d be happy to change over from rusqlite to limbo, at least for the async functionality.
Do you happen to know of a few situations where bloom filters are super useful? I need to identify when to use them.
I’m still lost on why they’re doing it.
After many years of using SO, I’ve started using ChatGPT for all of my programming questions and have not looked back once. For my usual “I know X is possible, but how do I do that in Y language” questions, it’s been a dream using ChatGPT.