go/hcl
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
hcl/zcl/zclsyntax/expression_vars.go

53 lines
1.0 KiB
Go
Raw Normal View History

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
package zclsyntax
// Generated by expression_vars_get.go. DO NOT EDIT.
// Run 'go generate' on this package to update the set of functions here.
import (
Relocate into the "zclconf" github account
2017-05-27 17:33:09 -07:00
"github.com/zclconf/go-zcl/zcl"
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
)
zclsyntax: first pass of parsing binary operations Not actually tested yet, since it can't be used until parseExpressionTerm works.
2017-05-31 18:54:54 -07:00
func (e *BinaryOpExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: start of expression parsing Conditional expression parsing is ostensibly implemented, but since it depends on the rest of the expression parsers -- not yet implemented -- it cannot be tested in isolation. Also includes an initial implementation of the conditional expression node, but this is also not yet tested and so may need further revisions once we're in a better position to test it.
2017-05-31 08:37:17 -07:00
func (e *ConditionalExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: stub of FunctionCallExpr This was added mainly just to spin the wheels of the Variables method generator. Its implementation is not yet complete.
2017-05-24 08:51:34 -07:00
func (e *FunctionCallExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: parsing of the index operator This can either be a traversal or a first-class node depending on whether the given expression is a literal. This exception is made to allow applications to conditionally populate only part of a potentially-large collection if the config is only requesting one or two distinct indices. In particular, it allows the following to be considered a single traversal from the scope: foo.bar[0].baz
2017-06-05 07:09:04 -07:00
func (e *IndexExpr) Variables() []zcl.Traversal {
return Variables(e)
}
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
func (e *LiteralValueExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: parsing and evaluation for object constructors
2017-06-04 16:14:02 -07:00
func (e *ObjectConsExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: RelativeTraversalExpr This is similar to ScopeTraversalExpr, but it traverses relative to the result of another expression rather than relative to a variable in the scope.
2017-06-04 18:40:15 -07:00
func (e *RelativeTraversalExpr) Variables() []zcl.Traversal {
return Variables(e)
}
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
func (e *ScopeTraversalExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: parsing of the two unary operators
2017-06-01 07:05:22 -07:00
zclsyntax: basic parsing and evaluation of string templates Control sequences are not yet supported, but interpolation sequences work.
2017-06-01 08:01:12 -07:00
func (e *TemplateExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: parsing and evaluation of tuple constructors
2017-06-04 14:22:51 -07:00
func (e *TupleConsExpr) Variables() []zcl.Traversal {
return Variables(e)
}
zclsyntax: parsing of the two unary operators
2017-06-01 07:05:22 -07:00
func (e *UnaryOpExpr) Variables() []zcl.Traversal {
return Variables(e)
}
Reference in New Issue Copy Permalink