is. One could hypothetically even add
attributes to allow for ordering(which is what the original cyclic
redundancy check is suppose to solve but makes things worse since it is
an ignorant algorithm).
The algorithm in druntime is correct, I'm sure you mean that the data
provided to the al
On 6/18/18 3:19 AM, Mr.Bingo wrote:
I have static this scattered throughout. Some are module static this and
some are struct and class.
In a test case I have reduced to a struct that uses a static this and I
get a cycle... even though, of course, the static this does nothing
accept internal
s. One could
hypothetically even add attributes to allow for ordering(which is
what the original cyclic redundancy check is suppose to solve but
makes things worse since it is an ignorant algorithm).
This type of method might be more feasible, a sort of static
main(). It does not check for static this of aggregates though
but gets around the CRC's banket fatal error.
I have static this scattered throughout. Some are module static
this and some are struct and class.
In a test case I have reduced to a struct that uses a static this
and I get a cycle... even though, of course, the static this does
nothing accept internal things.
It is very annoying to have
