test: [expected failures] EXPR fixtures needing implementation fixes - #164
Draft
leongdl wants to merge 1 commit into
Draft
test: [expected failures] EXPR fixtures needing implementation fixes#164leongdl wants to merge 1 commit into
leongdl wants to merge 1 commit into
Conversation
…in proposed/) Five parked fixtures with dual-implementation observations: the int64 param-default acceptance (both implementations), the openjd-rs 2^62 false-reject on task-range endpoints (Python accepts, spec admits any int64), the Python-only task-range 2^63 acceptance, the untyped membership acceptance in openjd-rs, and the unenforced 513-char let-identifier cap (both). Per-fixture output, spec citation, and classification in proposed/README.md. Companion to conformance-expr-lang-gaps. Signed-off-by: David Leong <116610336+leongdl@users.noreply.github.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.
Important
Expected-failure fixtures — do not expect these to pass. Spec-correct fixtures that FAIL against at least one current implementation, parked in
EXPR/proposed/(not discovered by the runner) so merging keeps the suite green. Per-fixture output, spec citation, and classification inproposed/README.md. Promote each fixture unchanged when its fix lands.Contents (5 fixtures, dual-implementation verified)
expr2.1.1--int64-overflow-param-default.invalid— INT paramdefault: 2^63accepted atcheckby BOTH implementations. The known live acceptance bug on the template-validation axis. Also blocked on restoring RFC 0005's dropped "64-bit Signed Integer Type" section to the published spec.expr2.1.1--int64-max-task-range.test— openjd-rs FALSELY REJECTS a valid task-range endpoint of 2^63−1 ("Integer overflow"); probing shows acceptance ends at 2^62−1. Python accepts and runs. The spec admits any int64. Rust-side bug, the mirror image of the acceptance bug.expr2.1.1--int64-overflow-task-range.invalid— task-range element 2^63: openjd-rs correctly rejects; the Python CLI accepts. Python-side bug.expr2.1.3--membership-element-type-mismatch.invalid—"a" in [1, 2]accepted by openjd-rs (evaluates to false at runtime); Python rejects at validation. §2.1.3 defines membership only as(list[T], T). Rust-side bug.3.6.1--let-identifier-513.invalid— a 513-char let identifier accepted by BOTH implementations; schema §3.6.1 caps<UserIdentifier>at 512. The 512 accept-twin is green in the companion PR.Companion to the green-fixture PR from branch
conformance-expr-lang-gaps.