Update 2021-05-15-What-the-error-handling-project-group-is-working-towards.md

yaahc · web-flow · commit af5dff831392 · 2021-05-20T09:27:10.000-07:00
diff --git a/posts/inside-rust/2021-05-15-What-the-error-handling-project-group-is-working-towards.md b/posts/inside-rust/2021-05-15-What-the-error-handling-project-group-is-working-towards.md
@@ -232,4 +232,4 @@ This recommendation only applies for error types that are exposed as part of lib
 
 We hope that these changes will significantly improve error handling experience provided by Rust. Error reporting will be more consistent and flexible and let the final application developer define how to format error reports for their specific use-case. It will be a lot harder to accidentally lose information when reporting errors. The tools for reporting errors will be more tightly integrated into the standard library and the language itself and we hope this will have extra benefits to the embedded ecosystem by more universally standardizing on the `Error` trait.
 
-So that's the plan for now, it's not the full plan of all the changes we'd like to make, but we think its the best first step. However, this is by no means set in stone and we're interested in getting feedback from the rest of the community so we can refine our design. So if you have thoughts please let us know, our project group repo is https://github.com/rust-lang/project-error-handling. Please feel free to open an issue or hop in our zulip stream and create a new topic to let us know what you think of this plan.
+So that's the plan for now, it's not the full plan of all the changes we'd like to make, but we think its the best first step. However, this is by no means set in stone and we're interested in getting feedback from the rest of the community so we can refine our design. So if you have thoughts please let us know, our project group repo is https://github.com/rust-lang/project-error-handling. Please feel free to [open an issue](https://github.com/rust-lang/project-error-handling/issues) or hop in our [zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/257204-project-error-handling) and create a new topic to let us know what you think of this plan.

Original file line number	Diff line number	Diff line change
`@@ -232,4 +232,4 @@ This recommendation only applies for error types that are exposed as part of lib`
`232`	`232`
`233`	`233`	We hope that these changes will significantly improve error handling experience provided by Rust. Error reporting will be more consistent and flexible and let the final application developer define how to format error reports for their specific use-case. It will be a lot harder to accidentally lose information when reporting errors. The tools for reporting errors will be more tightly integrated into the standard library and the language itself and we hope this will have extra benefits to the embedded ecosystem by more universally standardizing on the `Error` trait.
`234`	`234`
`235`		-So that's the plan for now, it's not the full plan of all the changes we'd like to make, but we think its the best first step. However, this is by no means set in stone and we're interested in getting feedback from the rest of the community so we can refine our design. So if you have thoughts please let us know, our project group repo is https://github.com/rust-lang/project-error-handling. Please feel free to open an issue or hop in our zulip stream and create a new topic to let us know what you think of this plan.
	`235`	+So that's the plan for now, it's not the full plan of all the changes we'd like to make, but we think its the best first step. However, this is by no means set in stone and we're interested in getting feedback from the rest of the community so we can refine our design. So if you have thoughts please let us know, our project group repo is https://github.com/rust-lang/project-error-handling. Please feel free to [open an issue](https://github.com/rust-lang/project-error-handling/issues) or hop in our [zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/257204-project-error-handling) and create a new topic to let us know what you think of this plan.