Re:Show HN: How to write a recursive descent parser
by munificent on Monday March 20, 2017 @12:19PM
(#13915383)
It's often faster to do as much as you can in a single pass, and language front ends are one of those areas where squeezing every last drop of performance out still really matters.
Re:Show HN: How to write a recursive descent parser
by Drup on Monday March 20, 2017 @01:17PM
(#13915889)
It's actually faster to separate things, because you will be able to implement them cleanly. Having a good pipeline such as "text -> AST -> typed AST -> IR -> .... -> ASM/VM code" is very valuable.
The costy parts are the middle layer optimization anyway. Typechecking time, for a well written type checker, is not that big.
Re:Show HN: How to write a recursive descent parser
by Ericson2314 on Tuesday March 21, 2017 @11:29AM
(#13923052)
I think incremental compilation is a far more elegant and efficient way to shorten debug cycles.
Also makes IDE stuff easier too.
Holy shit, people think that's a good idea? Pipelines please!