public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/98456] New: Use of std::get instead of get
@ 2020-12-27 21:07 moub.ahmed at hotmail dot com
  2020-12-28 20:11 ` [Bug libstdc++/98456] " redi at gcc dot gnu.org
  2020-12-29  1:20 ` moub.ahmed at hotmail dot com
  0 siblings, 2 replies; 3+ messages in thread
From: moub.ahmed at hotmail dot com @ 2020-12-27 21:07 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 98456
           Summary: Use of std::get instead of get
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: moub.ahmed at hotmail dot com
  Target Milestone: ---

This uses std::get :

https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/ranges#L3050

Whereas the standard uses get:

https://eel.is/c++draft/range.elements#view

Since std::get is not overloadable, this bug prevents custom tuple-like types
to interoperate with std::ranges::views::keys/values for instance.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/98456] Use of std::get instead of get
  2020-12-27 21:07 [Bug c++/98456] New: Use of std::get instead of get moub.ahmed at hotmail dot com
@ 2020-12-28 20:11 ` redi at gcc dot gnu.org
  2020-12-29  1:20 ` moub.ahmed at hotmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2020-12-28 20:11 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID
          Component|c++                         |libstdc++

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to moub.ahmed from comment #0)
> This uses std::get :
> 
> https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/
> ranges#L3050
> 
> Whereas the standard uses get:
> 
> https://eel.is/c++draft/range.elements#view

But when it says "get" it means "::std::get", see
https://eel.is/c++draft/contents#3

std::get is not a customization point.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/98456] Use of std::get instead of get
  2020-12-27 21:07 [Bug c++/98456] New: Use of std::get instead of get moub.ahmed at hotmail dot com
  2020-12-28 20:11 ` [Bug libstdc++/98456] " redi at gcc dot gnu.org
@ 2020-12-29  1:20 ` moub.ahmed at hotmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: moub.ahmed at hotmail dot com @ 2020-12-29  1:20 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from moub.ahmed at hotmail dot com ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to moub.ahmed from comment #0)
> > This uses std::get :
> > 
> > https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/
> > ranges#L3050
> > 
> > Whereas the standard uses get:
> > 
> > https://eel.is/c++draft/range.elements#view
> 
> But when it says "get" it means "::std::get", see
> https://eel.is/c++draft/contents#3
> 
> std::get is not a customization point.

I see. Thank you for the reply.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-12-29  1:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-27 21:07 [Bug c++/98456] New: Use of std::get instead of get moub.ahmed at hotmail dot com
2020-12-28 20:11 ` [Bug libstdc++/98456] " redi at gcc dot gnu.org
2020-12-29  1:20 ` moub.ahmed at hotmail dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).