https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268
--- Comment #4 from Christopher Yeleighton ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51539
--- Comment #5 from Christopher Yeleighton ---
Created attachment 51106
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51106=edit
Add Doxygen documentation to items in stl_function.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57840
--- Comment #9 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #8)
> Already fixed in r12-1964
>
> You know doxygen output isn't the only way to look at the code, right?
I thought merged commits refresh the published
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101306
Christopher Yeleighton changed:
What|Removed |Added
Resolution|--- |MOVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97001
--- Comment #3 from Christopher Yeleighton ---
The problem with a module-level @since is that std:: symbols are easiest to
locate in the std namespace (which provides a huge index of everything). Items
that are undocumented (there is a lot of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101268
--- Comment #3 from Christopher Yeleighton ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101307
--- Comment #1 from Christopher Yeleighton ---
(In reply to Christopher Yeleighton from comment #0)
> 1. Please remove the trailing comma from the title: Variable templates for
> type traits.
The trailing full stop, of course.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101307
Bug ID: 101307
Summary: Variable templates for type traits—corrections
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57840
--- Comment #6 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #3)
> I'm not sure why the comment on the primary template doesn't show up (maybe
> doxygen is only interested in a definition) and adding comments to the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57840
--- Comment #5 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #4)
> It shows up in the latest docs:
> https://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-api.20210701.html/a03925.
> html
>
> But several other classes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101306
--- Comment #2 from Christopher Yeleighton ---
(In reply to Christopher Yeleighton from comment #1)
> Interestingly enough, the problem does not affect https://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-api.20210701.html/
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101306
--- Comment #1 from Christopher Yeleighton ---
Interestingly enough, the problem does not affect https://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-api.20210701.html/a00209_source.html#l00060
>. It may be a timing issue—the latter document is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101306
Bug ID: 101306
Summary: positioning at line anchors is disturbed by the
navigation bar
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #14 from Christopher Yeleighton ---
Will you accept an improvement regarding an issue RESOLVED WONTFIX?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #12 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #10)
> Lots of things in our API docs are not in the standard, and lots of things
> in the standard are not in our API docs. If you're trying to use it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #8 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #6)
> While it would be nice if the libstdc++ API docs were 100% complete and
> described every piece of the library, that is never going to happen. If you
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #7 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Christopher Yeleighton from comment #3)
> > It should at least be present on the API page. The standard is not for
> > developers.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #4 from Christopher Yeleighton ---
(In reply to Jonathan Wakely from comment #1)
> It does exactly what the standard says it does. And it's self explanatory.
What is self-explanatory in is_integral_v? It could be "is integral
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #3 from Christopher Yeleighton ---
It should at least be present on the API page. The standard is not for
developers.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
Bug ID: 101258
Summary: std ::is_integral_v is undocumented
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99909
Christopher Yeleighton changed:
What|Removed |Added
CC||giecrilj at stegny dot 2a.pl
22 matches
Mail list logo
