Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove all uses of `unwrap` from our docs #34
Comments
sgrif
added
the
good first issue
label
Nov 30, 2015
This comment has been minimized.
masklinn
commented
Nov 30, 2015
|
How do you figure that'd work for examples using |
This comment has been minimized.
defyrlt
commented
Nov 30, 2015
|
I think that |
This comment has been minimized.
|
The example using |
This comment has been minimized.
|
I don't think we need to teach users how to handle error cases, but if we can avoid |
This comment has been minimized.
|
If this repo is going to be a popular place for people who newer to Rust (which I think it will be) it is important to show how to do it the right way. Or don't show it at all. Perhaps saving the Result as a variable and then a comment underneath about dealing with the result? |
This comment has been minimized.
hiimtaylorjones
commented
May 10, 2016
|
Shouldn't this be closed because of the above PR? If not, I'm more than willing to finish what work wasn't covered by #45! |
This comment has been minimized.
|
I think that there are still a few places left but I can't confirm at the moment. Feel free to let me know if that's the case |
hiimtaylorjones
referenced this issue
May 10, 2016
Closed
[Issue #34] - removing more instances of .unwrap() from documentation in favor of try!() #320
This comment has been minimized.
hiimtaylorjones
commented
May 12, 2016
•
|
Ah, I see what you're talking about. Upon doing a global project search for Anyways, I'm recommending closing this issue and my Issue #34 PR if everything is as it should be. Sorry for the misunderstanding! |
sgrif
closed this
May 12, 2016
This comment has been minimized.
|
Thanks! On Thu, May 12, 2016 at 7:31 AM Taylor Jones notifications@github.com
|
sgrif commentedNov 30, 2015
It's a terrible habit, and I agree that we shouldn't have it in our docs. I've gotten rid of a decent number recently, but I'd like to eliminate the rest in favor of
try!(this will take some annoying boilerplate in our doctests, but it's probably worth it).