December 02, 2019
https://issues.dlang.org/show_bug.cgi?id=340

--- Comment #18 from Basile-z <b2.temp@gmx.com> ---
I've noticed this meta issue when I used to fix bugs and I think it was only useful to show that there WAS a big problem in the compiler. There are more that are not listed here and I think there will always be a few cases that are not fixable. Out of order declarations, lazy semantic and multi passes will ALWAYS have problems although in most of the cases this gives great power and works fine.

People just gotta admit that not everything can work. The little pity is that we can't formally define what will not work.

--
March 21, 2020
https://issues.dlang.org/show_bug.cgi?id=340

Basile-z <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|b2.temp@gmx.com             |

--
February 25, 2022
https://issues.dlang.org/show_bug.cgi?id=340
Issue 340 depends on issue 3254, which changed state.

Issue 3254 Summary: [module] Module member visibility depends on declaration order https://issues.dlang.org/show_bug.cgi?id=3254

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--
1 2 3 4
Next ›   Last »