diff options
| author | Gary Guo <gary@garyguo.net> | 2026-09-23 15:06:15 +0100 |
|---|---|---|
| committer | Gary Guo <gary@garyguo.net> | 2026-09-28 12:43:17 +0100 |
| commit | 95593ed3616194c9498cc190cd1a3693ff4bca37 (patch) | |
| tree | 9c5201793e8a8d0d94c8dfab9a6ca335b42c96ac /tools/lib/python/kdoc/python_version.py | |
| parent | 73c1f157907cf23ef90e105f48c40fae75ee1008 (diff) | |
| download | linux-next-95593ed3616194c9498cc190cd1a3693ff4bca37.tar.gz linux-next-95593ed3616194c9498cc190cd1a3693ff4bca37.zip | |
rust: pin-init: internal: improve diagnostics robustness against panicking
Currently, if proc macro panicked, the diagnostics clean up is not
executed, and further invocation will cause the "DiagCtxt cannot be nested"
error. While we should aim to have no panics inside proc macros, producing
a sensible diagnostics message even when macro panicked is very useful for
developing.
Thus, catch proc macro panics and convert them to errors, and emit them
together with all diagnostics accumulated so far.
Ideally we would like panic location w/ line numbers being available as
well; however this is not currently implementable without overriding the
global panic hook.
Reviewed-by: Benno Lossin <lossin@kernel.org>
Link: https://patch.msgid.link/20260923140618.1978181-3-gary@kernel.org
Signed-off-by: Gary Guo <gary@garyguo.net>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
