In my opinion, this option and the syntactic sugar of initialising all the values from a single one is a confusing semantic choice. For example, how can you ensure that the following
vect : Double = 
is correct, or one value is missing…?
That is what I’ve been assuming, but that is how the full SmartSoft toolchain uses the DSL (1
.types per project, 1 CommObjectsRepository per
CommObjectsRepository per project). The fact that this is a practical choice only depends on the toolchain itself (for SmartSoft it is, but that may not be the case in general).
A different story is, if at the DSL design already, there is a constraint 1:1 mapping
CommObjectsRepository, or if multiple
CommObjectsRepository are allowed within the same file
So, the question is: should I assume this mapping constraint being a DSL design choice, or I am free to use it as I like?