On Sunday, 14 October 2018 at 03:26:33 UTC, Adam D. Ruppe wrote:
On Sunday, 14 October 2018 at 03:07:59 UTC, Chris Katko wrote:
For comparison, I just tested and grep uses about 4 MB of RAM
to run.
Running and compiling are two entirely different things.
Running the D regex code should be
On Sunday, 14 October 2018 at 02:44:55 UTC, Chris Katko wrote:
So wait, if their solution was to simply REMOVE std.regex from
isEmail.
That was ctRegex, which is different than regex.
That doesn't solve the regex problem at all. And from what I
read in that thread, this penalty is paid per
On Sunday, 14 October 2018 at 03:07:59 UTC, Chris Katko wrote:
For comparison, I just tested and grep uses about 4 MB of RAM
to run.
Running and compiling are two entirely different things. Running
the D regex code should be comparable, but compiling it is slow,
in great part because of
On Sunday, 14 October 2018 at 02:44:55 UTC, Chris Katko wrote:
On Friday, 12 October 2018 at 13:42:34 UTC, Alex wrote:
[...]
So wait, if their solution was to simply REMOVE std.regex from
isEmail. That doesn't solve the regex problem at all. And from
what I read in that thread, this penalty
On Friday, 12 October 2018 at 13:42:34 UTC, Alex wrote:
On Friday, 12 October 2018 at 13:25:33 UTC, Chris Katko wrote:
Like, insanely fat.
All I wanted was a simple regex. The second include a regex
function, my program would no longer compile "out of memory
for fork".
/usr/bin/time -v
On Friday, 12 October 2018 at 13:25:33 UTC, Chris Katko wrote:
Like, insanely fat.
All I wanted was a simple regex. The second include a regex
function, my program would no longer compile "out of memory for
fork".
/usr/bin/time -v reports it went from 150MB of RAM for D,
DAllegro, and
Like, insanely fat.
All I wanted was a simple regex. The second include a regex
function, my program would no longer compile "out of memory for
fork".
/usr/bin/time -v reports it went from 150MB of RAM for D,
DAllegro, and Allegro5.
To over 650MB of RAM, and from 1.5 seconds to >5.5
