You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if there is not adverse consequence on error messages (eg if we never need to look at bufferSource), would it make sense to get the source from from stdin instead of dumping to a temp file bufferSource ? nim can read from stdin using -
curious also whether compiler/nimeval could speed things up (calling compiler as a library instead of shelling out)
just posted https://forum.nim-lang.org/t/4048 : "how to get detailed compilation timing statistics (time spent in each phase, nim=>C=>.o=>binary) ? " to see whether we can measure bottlenecks in compile time speed
The text was updated successfully, but these errors were encountered:
timotheecour
changed the title
use nim - (reading from stdin) feature instead of writing to bufferSource
[SPEED] use nim - (reading from stdin) feature instead of writing to bufferSourceJul 14, 2018
timotheecour
changed the title
[SPEED] use nim - (reading from stdin) feature instead of writing to bufferSource
[SPEED] investigate options for improving compilation time in inim
Jul 14, 2018
if there is not adverse consequence on error messages (eg if we never need to look at
bufferSource
), would it make sense to get the source from fromstdin
instead of dumping to a temp filebufferSource
?nim
can read from stdin using-
curious also whether
compiler/nimeval
could speed things up (calling compiler as a library instead of shelling out)just posted https://forum.nim-lang.org/t/4048 : "how to get detailed compilation timing statistics (time spent in each phase, nim=>C=>.o=>binary) ? " to see whether we can measure bottlenecks in compile time speed
The text was updated successfully, but these errors were encountered: