[Bug libstdc++/101268] New: Refer manual readers to cppreference.com for API details

[Bug libstdc++/101268] New: Refer manual readers to cppreference.com for API details

[giecrilj at stegny dot 2a.pl]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

            Bug ID: 101268
           Summary: Refer manual readers to cppreference.com for API
                    details
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: giecrilj at stegny dot 2a.pl
  Target Milestone: ---

Since we have given up on documenting all standard library features we have
implemented (I mean patches are not welcome), we should add a reference to
cppreference.com to the product manual.

[Bug libstdc++/101268] Refer manual readers to cppreference.com for API details

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christopher Yeleighton from comment #0)
> (I mean patches are not welcome)

Have you actually tried submitting any? I only see bug reports from you, not
patches.

[Bug libstdc++/101268] Refer manual readers to cppreference.com for API details

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
c.f. PR 40380 comment 4

[Bug libstdc++/101268] Refer manual readers to cppreference.com for API details

[giecrilj at stegny dot 2a.pl]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

--- Comment #3 from Christopher Yeleighton <giecrilj at stegny dot 2a.pl> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Christopher Yeleighton from comment #0)
> > (I mean patches are not welcome)
> 
> Have you actually tried submitting any? I only see bug reports from you, not
> patches.

I have—the need to rebuild the whole thing before submitting had me in the
first half, not gonna lie :-(  It is so much easier in MSDN where the
documentation is completely separate.  

What I wanted to say is: resolving an issue as WONTFIX normally means that
patches would not be accepted.

[Bug libstdc++/101268] Refer manual readers to cppreference.com for API details

[giecrilj at stegny dot 2a.pl]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

--- Comment #4 from Christopher Yeleighton <giecrilj at stegny dot 2a.pl> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Christopher Yeleighton from comment #0)
> > (I mean patches are not welcome)
> 
> Have you actually tried submitting any? I only see bug reports from you, not
> patches.

VERBVM CARO FACTVM EST

<URL: https://gcc.gnu.org/bugzilla/attachment.cgi?id=51106 >

[Bug libstdc++/101268] Refer manual readers to cppreference.com for API details

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks. Please submit patches to the mailing lists as required by:
https://gcc.gnu.org/contribute.html#patches

Please capitalize "an" at the start of every sentence, and use markdown `...`
instead of @c ...

Please change the terms "superiority" and "inferiority" to something defined in
the standard.

The indentation of the new comments looks wrong too.