Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #83581

Re: ambiguous reference to 'find' in std and std::ranges namespaces

Show all headers | View raw

Am Thu, 14 Apr 2022 07:13:55 +0200
schrieb Christian Gollwitzer <auriocus@gmx.de>:

> Am 13.04.22 um 15:28 schrieb Juha Nieminen:
> > Juha Nieminen <nospam@thanks.invalid> wrote:  
> >> Paavo Helde <eesnimi@osa.pri.ee> wrote:  
> >>> In my implementation it appears to be implemented as a function
> >>> object, having operator() member functions. I guess the problem
> >>> is caused by this specific implementation, as the whole point of
> >>> niebloids seems to be the opposite (avoiding clashes with the
> >>> std:: namespace).  
> >>
> >> Perhaps a minimal example that replicates the mentioned behavior
> >> could illuminate if this is normal to-be-expected behavior, a
> >> problem with the library implementation, or perhaps even a problem
> >> with the compiler itself.  
> > 
> > (I mean a minimal example that doesn't use the standard library,
> > ie. a piece of code that itself demonstrates what's happening inside
> > the library for this error to happen.)  
> 
> Maybe the second example in this answer is helpful:
> 	
> 	https://stackoverflow.com/a/62929027

I have to admit that I am now more confused than before. Is the lookup
problem in my OP a bug or not? And if not and the niebloids are there to
avoid clashes why don't they do their job in my case? The first example
in the cited answer is equivalent to 

find(begin(v), end(v), 47)

in my OP. This works with either "using" directive but not both which I
understand since the iterator variant of find is declared in both. But
with my original "find" there should be no clash since nothing in std::
matches.

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ambiguous reference to 'find' in std and std::ranges namespaces Ralf Goertz <me@myprovider.invalid> - 2022-04-13 09:58 +0200
  Re: ambiguous reference to 'find' in std and std::ranges namespaces Paavo Helde <eesnimi@osa.pri.ee> - 2022-04-13 14:27 +0300
    Re: ambiguous reference to 'find' in std and std::ranges namespaces Bo Persson <bo@bo-persson.se> - 2022-04-13 14:21 +0200
      Re: ambiguous reference to 'find' in std and std::ranges namespaces Paavo Helde <eesnimi@osa.pri.ee> - 2022-04-13 15:31 +0300
    Re: ambiguous reference to 'find' in std and std::ranges namespaces Juha Nieminen <nospam@thanks.invalid> - 2022-04-13 13:26 +0000
      Re: ambiguous reference to 'find' in std and std::ranges namespaces Juha Nieminen <nospam@thanks.invalid> - 2022-04-13 13:28 +0000
        Re: ambiguous reference to 'find' in std and std::ranges namespaces Paavo Helde <eesnimi@osa.pri.ee> - 2022-04-13 17:26 +0300
        Re: ambiguous reference to 'find' in std and std::ranges namespaces Christian Gollwitzer <auriocus@gmx.de> - 2022-04-14 07:13 +0200
          Re: ambiguous reference to 'find' in std and std::ranges namespaces Ralf Goertz <me@myprovider.invalid> - 2022-04-14 08:57 +0200
            Re: ambiguous reference to 'find' in std and std::ranges namespaces Bo Persson <bo@bo-persson.se> - 2022-04-14 13:23 +0200
              Re: ambiguous reference to 'find' in std and std::ranges namespaces Paavo Helde <eesnimi@osa.pri.ee> - 2022-04-14 16:32 +0300
                Re: ambiguous reference to 'find' in std and std::ranges namespaces Bo Persson <bo@bo-persson.se> - 2022-04-14 18:30 +0200
              Re: ambiguous reference to 'find' in std and std::ranges namespaces Ralf Goertz <me@myprovider.invalid> - 2022-04-15 10:14 +0200
            Re: ambiguous reference to 'find' in std and std::ranges namespaces Manfred <noname@add.invalid> - 2022-04-14 15:02 +0200
  Re: ambiguous reference to 'find' in std and std::ranges namespaces Christian Hanné <the.hanne@gmail.com> - 2022-04-15 14:39 +0200

csiph-web