Ellery Newcomer wrote:
On 12/01/2009 02:35 PM, Chad J wrote:
No guarantees, but a lot of promise.
http://erdani.com/d/thermopylae.pdf
On page 114 of the draft, 14 of the pdf, in section 4.1.10, at the
bottom: notice how Andrei seems to be hedging on properties working
correctly.
Oh goodie.
Max Samukha wrote:
this.classinfo can be seen as a virtual function returning the
classinfo for the actual class instance and typeof(this).classinfo -
as a static function returning the classinfo of the compile-time type
of this (that is the class where it is called). So, your example
Removing a struct definition from the second mixin seems to fix the problem.
Is this a (known) bug?
The struct was only used within that template.
public struct S
{
enum LOCAL { ONE, TWO };
LOCAL local;
bool b = false;
StructOut s;
ENUM_OUT eo;
}
Saaa:
Is this a (known) bug?
It's generally better if you show a tiny compilable example that has the
problem.
Bye,
bearophile
bearophile wrote:
Saaa:
Is this a (known) bug?
It's generally better if you show a tiny compilable example that has the
problem.
Bye,
bearophile
I'm trying :)
I just hoped somebody would recognize it from my babbling
Tomorrow I'll continue my quest for the mall piece of code which will choke
the compiler.
Can't recreate the error in a small test project (5 modules).
I think the problem lies somewhere in between cyclic module imports, mixin
struct definitions and maybe the actual size of the class(1k) and its
complexity of interfaces(8).
One more thing:
The out of memory is before it can tell
