jmoiron plays the blues

6241024c to jigo add a printer to get a better understanding of how things are nested

bdc97d4f to jigo start list implementation, multiple map-elem map literals

4e2aa3ce to jigo get rid of exxtra prints

0efeeddd to jigo map exprs

2f2916ee to jigo failing wip on passing stack state along to teach level of parse exprs

a328b728 to jigo wip mul exprs

c6c76638 to jigo add some stub code for indexExpr, etc

75109395 to jigo add node stack, addexpr

694e70ca to jigo some pointless whitespace chagnes

@jmoiron @tinabeans "To think, you have to write. If you think without writing, you only think you're thinking." - Leslie Lamport

c600cff4 to jigo add strings and some missing bools and unary opers to the lexer, add some failing parser tests

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

forked code, Source Code for Go In Action examples

jmoiron/dotfiles 96ac71c · add environ for fast bootstrap

@jmoiron @asmedrano the surprise is the breakdown; imho pointers are foundational to computation, but these are often productive devs, not beginners

@jmoiron @tom_forsyth and/or implement a toy compiler/interpreter to learn how common language semantics are organized mechanically.

@jmoiron @goinggodotnet You still understand what they *are* though, just maybe not all the implications; the confusion I'm citing runs deeper.

9860dc11 to jigo start to formalize the grammar for expressions, literals, and types

@jmoiron One of biggest surprises I've had related to #golang is just how many developers there are who do not know about pointers even as a concept.

33533492 to jigo start varaible block parsing