Re: [PATCH] Remove note about C++ demangler from Rust documentation

[Eli Zaretskii <eliz@gnu.org>]

> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Tue, 10 Mar 2026 12:46:53 -0600
> 
> A note about the C++ demangler in the Rust documentation hasn't been
> accurate for a while.  Also, it probably isn't clear to users how this
> related to the next bit of text in the same bullet point.  This patch
> removes the obsolete comment.
> ---
>  gdb/doc/gdb.texinfo | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 63f6fe39a55..ceb69669ea6 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -18396,12 +18396,10 @@ to call generic functions or otherwise refer to generic items, you
>  will have to specify the type parameters manually.
>  
>  @item
> -@value{GDBN} currently uses the C@t{++} demangler for Rust.  In most
> -cases this does not cause any problems.  However, in an expression
> -context, completing a generic function name will give syntactically
> -invalid results.  This happens because Rust requires the @samp{::}
> -operator between the function name and its generic arguments.  For
> -example, @value{GDBN} might provide a completion like
> +In an expression context, completing a generic function name will give
> +syntactically invalid results.  This happens because Rust requires the
> +@samp{::} operator between the function name and its generic
> +arguments.  For example, @value{GDBN} might provide a completion like
>  @code{crate::f<u32>}, where the parser would require
>  @code{crate::f::<u32>}.

OK, thanks.

Approved-By: Eli Zaretskii <eliz@gnu.org>