Martin Atkins 33c3d6e5ad zclwrite: standardize on TokenSeq for all node parts ...

We'll use TokenSeq for everything, including sequences we expect to
contain only one token, mainly for consistency but also so that our local
"parser" doesn't need to care about whether the main parser is returning
one token or many.

2017-06-07 07:41:39 -07:00

..

ast.go

zclwrite: standardize on TokenSeq for all node parts

2017-06-07 07:41:39 -07:00

doc.go

zclwrite: stub of zcl code generation package

2017-05-29 16:05:34 -07:00

format.go

zclwrite: begin to flesh out public interface

2017-06-07 07:24:10 -07:00

native_node_sorter.go

zclwrite: foundations of the writer parser

2017-06-06 08:53:13 -07:00

parser_test.go

zclwrite: start to partition body items

2017-06-07 07:38:44 -07:00

parser.go

zclwrite: start to partition body items

2017-06-07 07:38:44 -07:00

public.go

zclwrite: begin to flesh out public interface

2017-06-07 07:24:10 -07:00

round_trip_test.go

zclwrite: method for writing tokens to a writer

2017-06-07 07:06:23 -07:00

tokens.go

zclwrite: Don't crash if EachToken called on a nil TokenSeq.

2017-06-07 07:39:01 -07:00