Martin Atkins 4e18e3a8a8 zcl: allow nil Variables in EvalContext ... it's acceptable to have "Variables" set to nil in an EvalContext, if a particular scope has no variables at all. If _no_ contexts in the chain have non-nil variables, this is considered to mean that variables are not allowed at all, which produces a different error message.		2017-06-16 07:15:14 -07:00
..
hclhil	Add MissingItemRange to zcl.BodyContent	2017-06-03 16:46:49 -07:00
json	json: parse strings as zclsyntax templates	2017-06-12 07:25:09 -07:00
zclsyntax	zclsyntax: "expanding" function arguments	2017-06-15 08:18:00 -07:00
diagnostic_text_test.go	Mechanism for introspection of source code for editors	2017-05-19 19:33:58 -07:00
diagnostic_text.go	Mechanism for introspection of source code for editors	2017-05-19 19:33:58 -07:00
diagnostic.go	Initial support for printing out diagnostics	2017-05-18 19:01:41 -07:00
didyoumean.go	zcl: Implement Traversal.TraverseAbs	2017-06-05 07:55:33 -07:00
doc.go	Initial stubs of the public API	2017-05-13 17:44:11 -07:00
eval_context.go	Update cty references to its new home in the zclconf github account	2017-05-27 17:35:44 -07:00
merged_test.go	Define Body.JustAttributes as returning Attributes	2017-05-21 15:43:41 -07:00
merged.go	Define Body.JustAttributes as returning Attributes	2017-05-21 15:43:41 -07:00
ops.go	zcl: Automatically convert key types when indexing	2017-06-05 07:39:14 -07:00
pos.go	zcl: Range.String should not be a pointer method	2017-06-11 08:37:28 -07:00
schema.go	json: start of low-level decoding	2017-05-19 19:33:58 -07:00
structure.go	Add MissingItemRange to zcl.BodyContent	2017-06-03 16:46:49 -07:00
traversal.go	zcl: allow nil Variables in EvalContext	2017-06-16 07:15:14 -07:00