Conversation
Constraints / Simple constraints paradigm articles (en+ru in lockstep): - add a Language section to Simple constraints linking the realizing constructions (the => statement for the consequence, the NONULL option for the definiteness constraint). - keep the simple-constraint comparison table tier-pure: the keyword-only "Statement" row becomes an abstract "Implementation" availability row. - sync EN/RU: link the default value to the Built-in classes anchor in EN as RU already does; align the EN Constraints CHECKED BY example comment. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CONSTRAINT and => statements (en+ru in lockstep), verified against the grammar and addConstraint/addFollows: - mark the event clause optional ([eventClause]) and note the global APPLY event is used when omitted (baseEventPE is fully optional, default APPLY). - CONSTRAINT: the PROPERTIES list holds expressions over the constraint condition's parameters (nonEmptyPropertyExpressionList), not plain property ids; rename to outExpr and describe accordingly. - CONSTRAINT: the MESSAGE value may be any parameterless expression (propertyExpression in an empty context), with a string literal or a parameterless property as examples. - => : document RESOLVE as two independent, combinable options ([RESOLVE [LEFT] [RIGHT]]), described as separate options, and word the prose accordingly. - => : fix the EN RESOLVE RIGHT equivalence example, which had the premise and consequence swapped (right resolution drops the premise when the consequence is dropped), matching RU and addFollows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Reviewers repeatedly flag ../<type>/<name>.md cross-type links as broken, assuming filesystem resolution. Record that the type-first layout uses these relative paths, that they resolve by the target's document id, and that they must not be treated as broken just because the literal path has no on-disk sibling. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.