needing to change the order of things at module level = compiler bug, right?
schveiguy at gmail.com
Sun Dec 8 18:01:03 UTC 2019
On 12/8/19 11:43 AM, DanielG wrote:
> I dustmite'd down my problem code, and it seems just changing the order
> of declarations makes the error go away. Specifically, moving a class
> declaration from the bottom of the file, to the top, allows it to
> compile. I also commented on two other things that can be changed to
> make it work - neither seemingly related to the error at hand.
Yes, if it can compile when you move things around, and the result is
*correct* (very important characteristic), then it's definitely a bug.
There should be no ordering requirements for module-level code.
More information about the Digitalmars-d-learn