You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/correctness.adoc
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -99,25 +99,25 @@ Note that this doesn't require any knowledge of the metamodels, as it just invol
99
99
This means that the serialization chunk doesn't need to be correct in the meta-referential nor in the meta-structural sense!
100
100
It should be alway possible to deserialize the serialization chunk into "`dynamic`"/"`reflective`" nodes, which could be useful in its own right.
101
101
102
-
// TODO describe when and how links should be resolved, etc.
102
+
**TODO:** describe when and how links should be resolved, etc.
103
103
104
104
=== Constraints
105
105
106
106
No constraint violations.
107
107
Constraints can only be checked with full knowledge of all metamodels involved, so meta-referential, meta-structural correctness is necessary for this.
108
108
Also: the more "`interesting`" constraints typically navigate across references, so structure-referential correctness would also be necessary.
109
109
It should be possible to come up with some kind of "`partial constraint checking`" that deals with unresolved references in a meaningful way -- possibly reporting warnings, rather than outright constraint violations.
110
-
// TODO come up with a "partial evaluation"-style semantics for navigating over an unresolved link, and e.g. type computation
110
+
**TODO:** come up with a "partial evaluation"-style semantics for navigating over an unresolved link, and e.g. type computation
111
111
112
112
Incorrectness is to be reported as a model with references to nodes, as well as an appropriate error message.
113
113
For multi-valued features, an index has to be included as well.
114
114
Recovery is more-or-less irrelevant from a technical standpoint, but incorrectness might obstruct/impede code generation, interpretation, type computation, etc.
115
115
116
116
117
-
// TODO example of how to report violations of all stated kinds
117
+
**TODO:** example of how to report violations of all stated kinds
0 commit comments