https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
Manuel López-Ibáñez changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #6 from Manuel Lóp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
--- Comment #5 from Daniel Frey ---
I don't know if it is possible for GCC to know, but it feels like it should
know. If one type needs to instantiate another type, this goes on until either
everything worked or GCC stops to instantiate a sub-typ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
--- Comment #4 from Manuel López-Ibáñez ---
(In reply to Daniel Frey from comment #3)
> instead. I'd still like to see GCC to hint at the loop when trying to
> complete types where the completion of A requires a completed B and the
> completion o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
--- Comment #3 from Daniel Frey ---
Just a reminder that the error message is basically still the same with GCC 4.9
and does not help to understand the cause of the error. Especially real-world
cases are therefore extremely hard to understand!
I
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
--- Comment #2 from Daniel Frey 2011-10-22 13:19:02 UTC
---
I think I'm asking for the word "recursion" or "recursive" in the error
message, bonus points for clearly identifying the cycle. The example is
obviously too simple to demonstrate the us
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |enhancement
Keywords||diagnosti
