Why we should not enable a slow DFA by default

Richard (Rikki) Andrew Cattermole richard at cattermole.co.nz
Fri Dec 19 08:40:34 UTC 2025

Previous message: Why we should not enable a slow DFA by default
Next message: Why we should not enable a slow DFA by default
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Out of curiosity I wanted to know how many functions were @safe before 
and after the extra 2 passes took place.

Before: 2900 out of 6595

After: 106 out of 1103

That is a pretty big reduction.

Previous message: Why we should not enable a slow DFA by default
Next message: Why we should not enable a slow DFA by default
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Digitalmars-d mailing list