From b721e4838d178e32783f49e4d69185071e86e6fa Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Mon, 25 Nov 2019 12:27:16 +0100 Subject: [PATCH] tiny edits --- ralf/_posts/2019-11-25-how-to-panic-in-rust.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ralf/_posts/2019-11-25-how-to-panic-in-rust.md b/ralf/_posts/2019-11-25-how-to-panic-in-rust.md index 66ca0ab..83216ad 100644 --- a/ralf/_posts/2019-11-25-how-to-panic-in-rust.md +++ b/ralf/_posts/2019-11-25-how-to-panic-in-rust.md @@ -151,7 +151,7 @@ However, even with that future extension, I think we have the invariant that whe I wonder if there is any case where *both* fields will be useful -- and if not, couldn't we encode that by making them two variants of an `enum`? There are probably good reasons against that proposal and for the current design; it would be great to get them documented somewhere. :) -There is a lot more to say, but at this point, I invite you to follow the links to the source code that I included above and read the local comments. -With the high-level structure in mind, those comments should be able to fill out any missing details. -If people think this information would be worth putting somewhere more permanently, I'd be happy to work this blog post into some form of docs -- I am not sure what would be a good place for those, though. +There is a lot more to say, but at this point, I invite you to follow the links to the source code that I included above. +With the high-level structure in mind, you should be able to follow that code. +If people think this overview would be worth putting somewhere more permanently, I'd be happy to work this blog post into some form of docs -- I am not sure what would be a good place for those, though. And if you find any mistakes in what I wrote, please let me know! -- 2.30.2