public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/111748] New: GCC does not understand partial ordering between non-constrained and constrained templates for specialization
@ 2023-10-09 22:24 jeanmichael.celerier at gmail dot com
  0 siblings, 0 replies; only message in thread
From: jeanmichael.celerier at gmail dot com @ 2023-10-09 22:24 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 111748
           Summary: GCC does not understand partial ordering between
                    non-constrained and constrained templates for
                    specialization
           Product: gcc
           Version: 13.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jeanmichael.celerier at gmail dot com
  Target Milestone: ---

Consider: 

    #include<concepts>

    template<typename>
    void foo() { }

    template<std::integral> 
    void foo() { }

    template<> 
    void foo<bool>() { }

    int main() { foo<bool>(); }


According to the answers I got in https://stackoverflow.com/questions/77261120/
GCC should be able to compile this code, yet it fails due to a supposed
ambiguity between 

    template<typename>
    void foo() { }

and

    template<std::integral> 
    void foo() { }

as the base of foo<bool>

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2023-10-09 22:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-09 22:24 [Bug c++/111748] New: GCC does not understand partial ordering between non-constrained and constrained templates for specialization jeanmichael.celerier at gmail 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).