hcl/hclsyntax/generate.go

package hclsyntax

//go:generate go run expression_vars_gen.go
//go:generate ruby unicode2ragel.rb --url=http://www.unicode.org/Public/9.0.0/ucd/DerivedCoreProperties.txt -m UnicodeDerived -p ID_Start,ID_Continue -o unicode_derived.rl
//go:generate ragel -Z scan_tokens.rl
//go:generate gofmt -w scan_tokens.go
//go:generate ragel -Z scan_string_lit.rl
//go:generate gofmt -w scan_string_lit.go
//go:generate stringer -type TokenType -output token_type_string.go
Move the zcl package and its two parsing subpackages to "hcl" names This is a super-invasive update since the "zcl" package in particular is referenced all over. There are probably still a few zcl references hanging around in comments, etc but this takes care of most of it. 2017-09-11 16:40:37 -07:00			`package hclsyntax`
zclsyntax: Generate "Variables" implementations for all Expressions The implementation of Variables will be identical for every Expression implementation since we just wrap our AST-walk-based "Variables" function to do the work. Rather than manually copy-pasting the declaration for each expression type, instead we'll generate this programmatically using "go generate". This will need to be re-run each time a new expression node type is added, in order to make it actually implement the Expression interface. 2017-05-24 08:50:44 -07:00
			`//go:generate go run expression_vars_gen.go`
zclsyntax: identifiers in the scanner 2017-05-28 09:16:53 -07:00			`//go:generate ruby unicode2ragel.rb --url=http://www.unicode.org/Public/9.0.0/ucd/DerivedCoreProperties.txt -m UnicodeDerived -p ID_Start,ID_Continue -o unicode_derived.rl`
zclsyntax: scanner to return whole token slice at once On reflection, it seems easier to maintain the necessary state we need by doing all of the scanning in a single pass, since we can then just use local variables within the scanner function. 2017-05-28 07:11:24 -07:00			`//go:generate ragel -Z scan_tokens.rl`
			`//go:generate gofmt -w scan_tokens.go`
hclsyntax: rewrite string literal decoder with ragel Fuzz testing revealed that there were a few different crashers in the string literal decoder, which was previously a rather-unweildy hand-written scanner with manually-implemented lookahead. Rather than continuing to hand-tweak that code, here instead we use ragel (which we were already using for the main scanner anyway) to partition our string literals into tokens that are easier for our decoder to wrangle. As a bonus, this also makes our source ranges in our diagnostics more accurate. 2018-02-04 18:35:42 -08:00			`//go:generate ragel -Z scan_string_lit.rl`
			`//go:generate gofmt -w scan_string_lit.go`
zclsyntax: run stringer after other generators stringer is more sensitive to certain errors than other generators, so by running it last we give the other generators a chance to get things straight before we ask stringer to run. 2017-06-05 07:04:26 -07:00			`//go:generate stringer -type TokenType -output token_type_string.go`