Nice, I think you strike a nice balance regarding speed of explanations. I am still in a different industry but find myself increasingly more motivated for rust programming.
Thanks, that's exactly what I want to achieve with my videos. Quick enough to not bore people, but slow and thorough enough to be accessible for beginners and intermediates.
Fantastic breakdown on how to implement error handling well. I learned a ton with this video, specially the automatic conversion using From and the ? operator. Thanks for this Video! I'm now wondering what is the best way to handle REST API responses errors. I generally like to use Serde and Reqwest, but I'm still a bit fussy on how to convert error payloads back to a type that I can return as an error. Like, I have my type for the success case so Serde can deserialise, but how to properly deserialise the payload for a safe type when I get an error instead from the JSON payload? Thanks again!
Personally I would never shadow built-in Result type. That saves very little typing while making function signatures way harder to understand for other programmers while skimming the code.
lets assume file contains billion of records, where second line is "bad". will map/collect iterate over all lines to fail later or it stops on first error?
CvsError would not pass any corporate inspection due to lack of consistency. FileIsEmpty but LineTooShort instead of LineIsTooShort? FileNotExistant (adjective) but CouldNotParseLine (verb) instead of LineNotParseable (adjective)? FileIsEmpty (present) but CouldNotOpenFile (past)? I know this was only toy code, but consistent error naming is super important to learn since day 0. Another reason why it would fail inspection is uncapped error size in CouldNotParseValue(String). That can be poisonous for log collecting and processing systems. Errors that copy user input as part of message should always be sanitized and capped.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
A great demo of custom error handling in Rust! Eagerly awaiting next video in the Advanced Rust series...
I see my green tea boi?
I click!
Another banger brother 💪❤
Nice, I think you strike a nice balance regarding speed of explanations. I am still in a different industry but find myself increasingly more motivated for rust programming.
Thanks, that's exactly what I want to achieve with my videos. Quick enough to not bore people, but slow and thorough enough to be accessible for beginners and intermediates.
Fantastic breakdown on how to implement error handling well. I learned a ton with this video, specially the automatic conversion using From and the ? operator. Thanks for this Video!
I'm now wondering what is the best way to handle REST API responses errors.
I generally like to use Serde and Reqwest, but I'm still a bit fussy on how to convert error payloads back to a type that I can return as an error.
Like, I have my type for the success case so Serde can deserialise, but how to properly deserialise the payload for a safe type when I get an error instead from the JSON payload?
Thanks again!
Very well explained. Thanks
You're welcome! How long have you been programming Rust?
@@GreenTeaCoding about a year now. How to handle errors in a nice way was always a challenge. now you learned me how to do it
@@ChuvChuvee Yeah, the first year in Rust can be really rough. It get's really beautiful afterwards though!
Personally I would never shadow built-in Result type. That saves very little typing while making function signatures way harder to understand for other programmers while skimming the code.
can you please try to create tutorial on axum framework?
lets assume file contains billion of records, where second line is "bad". will map/collect iterate over all lines to fail later or it stops on first error?
CvsError would not pass any corporate inspection due to lack of consistency. FileIsEmpty but LineTooShort instead of LineIsTooShort? FileNotExistant (adjective) but CouldNotParseLine (verb) instead of LineNotParseable (adjective)? FileIsEmpty (present) but CouldNotOpenFile (past)? I know this was only toy code, but consistent error naming is super important to learn since day 0.
Another reason why it would fail inspection is uncapped error size in CouldNotParseValue(String). That can be poisonous for log collecting and processing systems. Errors that copy user input as part of message should always be sanitized and capped.
You seem to be very knowledgeable and experienced, an I appreciate your feedback. I will try to improve on this points next time, thanks!
Do you plan on sharing the code from this example?
Fair request :)
I added the Github repo link in the description.
I use anyhow
How much do you charge an hourly session to teach advanced Rust? I am a Rust Dev
I am currently not offering paid sessions.