News for hackers. Stuff that matters.
Re:Why not to use (f)lex, yacc or bison by atombender on Thursday March 05, 2020 @12:36PM (#22495846)
Go doesn't use a generated parser. Both the parser and the lexer are hand-written:

https://github.com/golang/go/blob/master/src/go/parser/parse...

https://github.com/golang/go/blob/master/src/go/scanner/scan...

Why did you think it was generated?

Re:Why not to use (f)lex, yacc or bison by minieggs on Thursday March 05, 2020 @02:18PM (#22497026)
If you look closely at the Go code you'll see it was once C code generated by some parser generater (which I assume was Bison). Believe it was Russ Cox that wrote a program that transformed the generated C code into Go.

Edit: I forked the compiler a while ago to add maybe types (a la Rust result). Looks like the compiler code has changed quite a bit from when I was playing w/ it.

Re:Why not to use (f)lex, yacc or bison by atombender on Thursday March 05, 2020 @02:27PM (#22497134)
That's a long time ago. You can see vestiges of it here and there (mostly in deeper areas of the compiler, which goes all the way back to Plan 9), but the parser now looks very clean.
Re:Why not to use (f)lex, yacc or bison by minieggs on Thursday March 05, 2020 @02:37PM (#22497249)
Very true and agree. Parser is in good shape.
Re:Why not to use (f)lex, yacc or bison by 0xjnml on Saturday March 07, 2020 @09:15AM (#22511607)
FTR: The go/parser package was _never_ used by the Go compiler. It used to be a yacc generated one when the compiler itself was in C. Then it was all mechanically translated to Go. And finally, a hand written lexer and parser were adopted, but different from the ones in the stdlib.