370b0a1406
This is an initial pass at property binding. For all stack instantiations, we must verify that the set of properties supplied are correct. We also must remember the bound property information so that code-generation has all of the information it needs to generate correct code (including capability refs). This entails: * Ensuring required properties are provided. * Expanding missing properties that have Default values. * Type-checking that supplied properties are of the right type. * Expanding property values into AST literal nodes. To do this requires a third AST pass in the semantic analysis part of the compiler. In the 1st pass, dependencies aren't even known yet; in the 2nd pass, dependencies have not yet been bound; therefore, we need a 3rd pass, which can depend on the full binding information for the transitive closure of AST nodes and dependencies to have been populated with types. There are a few loose ends in here: * We don't yet validate top-level stack properties. * We don't yet validate top-level stack base type properties. * We don't yet support complex schema property types. * We don't yet support even "simple" complex property types, like `[ string ]`. * We don't yet support strongly typed capability property types (just `service`). That said, I am going to turn to writing a few tests for the basic cases, and then resume to finishing this afterwards (tracked by marapongo/mu#25). |
||
|---|---|---|
| .. | ||
| ast | ||
| compiler | ||
| diag | ||
| encoding | ||
| errors | ||
| util | ||
| workspace | ||