summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorGary Guo <gary@garyguo.net>2026-09-28 18:32:20 +0100
committerGary Guo <gary@garyguo.net>2026-09-30 15:56:22 +0100
commitd99668f5ed5839a1a8f061dd5a47ab5d0c7dac74 (patch)
tree9aa5fe4ab1008b4bcd98a6defec1dc09c5df4b39 /tools/lib/python/kdoc/python_version.py
parent158e85db3375c4b0b66223dee7aae16f2357aada (diff)
downloadlinux-next-d99668f5ed5839a1a8f061dd5a47ab5d0c7dac74.tar.gz
linux-next-d99668f5ed5839a1a8f061dd5a47ab5d0c7dac74.zip
rust: pin-init: internal: init: improve diagnostics from field checks
Use span of the field name for generated alignment and field duplication checks. This avoids pointing diagnostics to the full macro invocation, but just the part of it going wrong. Before the change: error[E0062]: field `0` specified more than once --> tests/ui/compile-fail/init/tuple_duplicate_field.rs:7:37 | 7 | let _ = pin_init!(Tuple { 0: 1, 0: 2, 1: 3 }); | ------------------------^------------ | | | | | used more than once | first use of `0` After the change: error[E0062]: field `0` specified more than once --> tests/ui/compile-fail/init/tuple_duplicate_field.rs:7:37 | 7 | let _ = pin_init!(Tuple { 0: 1, 0: 2, 1: 3 }); | - ^ used more than once | | | first use of `0` Link: https://patch.msgid.link/20260928-dev-pin-init-sync-v1-2-e591c8e9cf0e@garyguo.net 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