New proposed text resolving issue 71 (Guarded expressions)#230
Merged
ndw merged 1 commit intoqt4cg:masterfrom Nov 15, 2022
Merged
New proposed text resolving issue 71 (Guarded expressions)#230ndw merged 1 commit intoqt4cg:masterfrom
ndw merged 1 commit intoqt4cg:masterfrom
Conversation
ChristianGruen
approved these changes
Nov 3, 2022
Contributor
ChristianGruen
left a comment
There was a problem hiding this comment.
Clear approval. I wondered if it’s side-effects or side effects, but I’m the wrong person to judge.
Contributor
|
Accepted at meeting 011, 15 November 2022 |
ndw
added a commit
to ndw/qtspecs-xslt4
that referenced
this pull request
Nov 16, 2022
…ions New proposed text resolving issue 71 (Guarded expressions)
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
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.
The discussion on issue 71 was very wide-ranging and went off into a number of tangents. This PR attempts to resolve the issue initially raised (order of evaluation of predicates) in a general way by introducing the notion of guarded expressions. This also provides a proposed solution to the question of "short-cutting" and/or expressions - essentially, an optimiser can change the order of evaluation, but doing so must not introduce dynamic errors that would not occur in a short-cutted evaluation.