rustdoc: Catch fatal errors when syntax highlighting #68326
Conversation
For some errors the lexer will unwind so we need to handle that in addition to handling `token::Unknown`.
|
The "simpler" solution in here I arrived to was to simply update the pulldown-cmark version. However we're still waiting for the new release since that when I updated to the current one, I discovered some bugs. What do you think? If you still prefer to go on with this PR, please at least add a TODO or equivalent in the code and open an issue so we can remove this catch. |
I think you're thinking of a different issue. The syntax highlighting has nothing to do with pulldown-cmark. The unwinding here is coming from rustc's lexer and according to #63288 it's intentional, at least for now. |
|
My bad! Then looks all good to me, thanks! @bors: r+ |
|
📌 Commit 79061d0 has been approved by |
bors
added
the
S-waiting-on-bors
…rors, r=GuillaumeGomez rustdoc: Catch fatal errors when syntax highlighting For some errors the lexer will unwind so we need to handle that in addition to handling `token::Unknown`. Fixes rust-lang#56885 r? @GuillaumeGomez
Rollup of 5 pull requests Successful merges: - #68326 (rustdoc: Catch fatal errors when syntax highlighting) - #68335 (Remove real_drop_in_place) - #68353 (Remove `rustc_error_codes` deps except in `rustc_driver`) - #68357 (rustdoc: Fix handling of compile errors when running `rustdoc --test`) - #68365 (Clean up error codes) Failed merges: r? @ghost
jyn514
added
the
T-rustdoc
For some errors the lexer will unwind so we need to handle that in addition to handling
token::Unknown.Fixes #56885
r? @GuillaumeGomez