Martin Atkins 639dff15c3 lang/eval: Clear some linter warnings ... Based on discussion so far it seems that we have consensus about merging the lang/eval and engine-related commits that precede this one as a starting point for ongoing work in future (hopefully smaller) PRs. This commit therefore mostly just acknowledges a small amount of unused code in a way that it won't cause linter noise, since the future work is likely to make these be used and so it'll be helpful to have them around as examples to build on. (Which is, after all, the whole point of merging this as dead code in the first place!) This does _actually_ remove an old, now-redundant declaration of the "compiled module instance" interface though, since that eventually ended up in a different place and I just forgot to clean up this initial form of it in later refactoring. Signed-off-by: Martin Atkins <mart@degeneration.co.uk>		2025-10-27 10:15:41 -07:00
..
attribute.go	lang/eval: Rework how module calls work	2025-10-27 10:15:41 -07:00
closure.go	lang/eval+lang/exprs: More exprs.EvalError markings	2025-10-27 10:15:41 -07:00
doc.go	lang/exprs: Expression evaluation helpers	2025-10-27 10:15:41 -07:00
evalable.go	lang/eval: Clear some linter warnings	2025-10-27 10:15:41 -07:00
evaluate.go	lang/eval+lang/exprs: More exprs.EvalError markings	2025-10-27 10:15:41 -07:00
example_test.go	lang/eval: Beginnings of a different way to handle config eval	2025-10-27 10:15:41 -07:00
marks.go	configgraph: Some unit tests for some "Value" methods	2025-10-27 10:15:41 -07:00
scope.go	lang/eval: Beginnings of a different way to handle config eval	2025-10-27 10:15:41 -07:00
symbol_table.go	lang/exprs: Expression evaluation helpers	2025-10-27 10:15:41 -07:00
traversals.go	lang/eval: Beginnings of a different way to handle config eval	2025-10-27 10:15:41 -07:00
valuer.go	lang/eval: Start of supporting module calls	2025-10-27 10:15:41 -07:00