f79e6726cc
Add that the ? operator works with From<Err> ( #1059 )
2023-08-09 16:48:15 +02:00
98be9e149c
Talk about options in ? chapter ( #600 )
...
* Talk about options in `?` chapter
* Combine Option and Result examples
* Update try-operator.md
* Remove semicolon from expansion
* Focus on expansion of `expr?`
* Update try-operator.md
* Update try-operator.md
---------
Co-authored-by: Martin Geisler <mgeisler@google.com >
2023-07-28 13:48:58 +02:00
46a38bc67a
Error is not yet available in core on stable ( #1005 )
2023-07-18 11:02:24 +02:00
bd98a829c6
Fix typo in try-operator.md ( #916 )
2023-07-06 15:25:37 +01:00
aba7fd7f56
Simplify error handling pages ( #851 )
...
This makes the `use` statements more consistent and shortens some
variable names.
2023-06-22 16:27:06 +02:00
c1ad97c659
Fix example to build and run ( #838 )
2023-06-21 09:48:05 +01:00
6ade739651
Ensure code blocks are editable ( #597 )
...
We should default to making code blocks editable: this ensures
consistent syntax highlighting (see #343 ) and it allows the instructor
to freely edit anything they want.
2023-04-27 23:45:41 +02:00
c0d03bd86b
Consistently use err for the error value ( #599 )
2023-04-27 19:10:49 +02:00
5cdb73387f
Inline format vars to make the format str simpler ( #551 )
2023-04-06 12:00:10 +02:00
7a22d5567a
Don't allocate in success case ( #506 )
...
`format!` was being called (and allocating a string) even in the success case.
2023-03-15 09:06:35 +01:00
1be641203e
Split out example to separate page. ( #319 )
...
The example is quite long and so the page didn't easily fit on the
same screen as the explanation
2023-02-03 10:12:31 +00:00
27b6165202
Implement Error.
2023-01-27 17:54:37 +00:00
caaca140ca
Another note for anyhow.
2023-01-27 17:54:37 +00:00
79f5f0dade
Add slide about Box<dyn Error> before introducing anyhow.
2023-01-27 17:54:37 +00:00
e5c97e12cb
No need for thiserror as well as anyhow.
2023-01-27 17:54:37 +00:00
9fa0e89e90
It makes no sense to use both return and ?.
2023-01-27 17:54:37 +00:00
52d28b155b
Mention std::error::Error in speaker notes, and other useful traits.
2023-01-27 17:54:37 +00:00
617f4e2bb7
Update error-contexts.md ( #251 )
...
* Update error-contexts.md
Adding more speaker notes about `anyhow`.
* Add markup
Co-authored-by: Martin Geisler <martin@geisler.net >
2023-01-24 07:33:03 +00:00
543cad59e4
Update result.md ( #250 )
...
* Update result.md
Adding a speaker note that `Result` documentation is a recommended read.
* Adding a note why `Result` encourages error checking.
* Wordsmithing
Co-authored-by: Andrew Walbran <qwandor@google.com >
2023-01-23 13:47:41 +00:00
492037641e
fix Cargo.toml syntax ( #190 )
2023-01-20 11:28:38 +01:00
acdf00ae6e
Add speaker notes about error examples
2023-01-11 18:14:58 -08:00
68eed5b4f2
Error handling: clarify printing of Result
...
Two examples may print either `Ok(username)` or `Err(error)`.
This commit clarifies this fact.
2023-01-06 12:35:05 -08:00
9a68434cac
Merge pull request #49 from ilyagr/patch-1
...
`anyhow`: Remove `ReadUsernameError::IoError`
2023-01-05 15:57:17 +01:00
e1c670c4a8
Fix a typo in result.md
...
"have already see" -> "have already seen"
2023-01-05 14:41:40 +06:00
8d36a3bdd3
fix typo in deriving-error-enums.md
2023-01-03 21:18:30 -08:00
c15e84f63e
More precise phrasing of what ? expands to
...
As per the suggestion from @QuineDot in #65 .
2022-12-27 18:09:54 +01:00
5ce7a08f0e
anyhow: say this example has fewer custom types
2022-12-23 13:35:40 -08:00
894e694cdb
anyhow: Remove ReadUsernameError::IoError
...
As far as I understand, the example with the `anyhow` example
does not use its special `IoError` anymore, unlike the previous
example with just `thiserror`.
I think this should be made clear. I considered just adding a
`// Now unused` comment, but I think ti's clearer to just remove
the unused code.
2022-12-23 13:32:03 -08:00
c212a473ba
Publish Comprehensive Rust 🦀
2022-12-21 16:38:28 +01:00
