https://gcc.gnu.org/g:56ef73fc1ea87b4fe5e88ed83854e91c5e3110ee
commit r17-5701-g56ef73fc1ea87b4fe5e88ed83854e91c5e3110ee Author: Pierre-Emmanuel Patry <[email protected]> Date: Fri Oct 23 12:14:44 2026 +0200 gccrs: Document glob containers path This path was not documented and usually unexpected. It lead to various headache during debugging sessions as the nullopt return value look out of place. gcc/rust/ChangeLog: * resolve/rust-name-resolution-context.hxx: Document non glob container path. Signed-off-by: Pierre-Emmanuel Patry <[email protected]> Diff: --- gcc/rust/resolve/rust-name-resolution-context.hxx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/gcc/rust/resolve/rust-name-resolution-context.hxx b/gcc/rust/resolve/rust-name-resolution-context.hxx index f5af7b3fa670..a92f15d7b40e 100644 --- a/gcc/rust/resolve/rust-name-resolution-context.hxx +++ b/gcc/rust/resolve/rust-name-resolution-context.hxx @@ -345,6 +345,10 @@ NameResolutionContext::resolve_segments ( } else { + // Non glob containers such as structures, we insert the + // segment but we let the type checker handle the rest since + // it has to resolve methode resolution & cie + // FIXME: Resolve segments always resolves in the Types NS // correct? If so, we should remove the template parameter for // this function - and use NS::Types directly here instead of
