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
cue-lang/cue#1470 made me realize that i had an erroneous assumption about how cue.Value.Subsume() worked. It's OK, even preferable that there's a simpler definition of it than my erroneous assumption allowed for, but it forces us to make a decision with Thema: should the addition of a new required field that does have a default value be considered a backwards compatible change, and therefore be allowed within a sequence?
My initial inclination is to say that we do, but the implications of this choice are considerable.
(TODO write up the implications re: default values, de/hydration, and assigning semantics to the state space)
invariantsInvolves the definition or enforcement of a key system invariant
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
cue-lang/cue#1470 made me realize that i had an erroneous assumption about how
cue.Value.Subsume()
worked. It's OK, even preferable that there's a simpler definition of it than my erroneous assumption allowed for, but it forces us to make a decision with Thema: should the addition of a new required field that does have a default value be considered a backwards compatible change, and therefore be allowed within a sequence?My initial inclination is to say that we do, but the implications of this choice are considerable.
(TODO write up the implications re: default values, de/hydration, and assigning semantics to the state space)
Beta Was this translation helpful? Give feedback.
All reactions