30b7040e95
Previously we were making an invalid assumption in evaluating module call references (like module.foo) that the module must exist, which is incorrect for that particular case because it's a reference to a child module, not to an object within the current module. However, now that we have the mechanism for static validation of references, we'll deal with this one there so it can be caught sooner. That then makes the original assumption valid, though for a different reason. This is verified by two new context tests for validation: - TestContext2Validate_invalidModuleRef - TestContext2Validate_invalidModuleOutputRef |
||
|---|---|---|
| .. | ||
| testdata/config-fixture | ||
| format.go | ||
| repl.go | ||
| session.go | ||
| session_test.go | ||