ed0710dd0b
The more I live with the current system, the more I prefer "properties" to "parameters" for stacks and services. Although it is true that these things are essentially construction-time arguments, they manifest more like properties in the way they are used; in fact, if you think of the world in terms of primary constructors, the distinction is pretty subtle anyway. For example, when creating a new service, we say the following: services: private: some/service: a: 0 b: true c: foo This looks like a, b, and c are properties of the type some/service. If, on the other hand, we kept calling these parameters, then you'd arguably prefer to see the following: services: private: some/service: arguments: a: 0 b: true c: foo This is a more imperative than declarative view of the world, which I dislike (especially because it is more verbose). Time will tell whether this is the right decision or not ... |
||
---|---|---|
.. | ||
backends | ||
core | ||
predef | ||
testdata | ||
binder.go | ||
binder_test.go | ||
common_test.go | ||
compiler.go | ||
compiler_test.go | ||
opts.go | ||
parser.go | ||
parsetree.go | ||
parsetree_test.go | ||
symbols.go |