Skip to content

chore(phel): track dev-main for assert-expr p/thrown? compat#17

Merged
Chemaclass merged 1 commit into
mainfrom
chore/track-phel-dev-main
May 29, 2026
Merged

chore(phel): track dev-main for assert-expr p/thrown? compat#17
Chemaclass merged 1 commit into
mainfrom
chore/track-phel-dev-main

Conversation

@Chemaclass

Copy link
Copy Markdown
Member

Why

The v0.40.0 release predates the phel.test/assert-expr signature change that the suite's p/thrown? portability shim depends on:

  • v0.40.0 tag: (defmethod assert-expr 'thrown? [form message] ...) — arg order [form message], dispatch on 1st arg.
  • dev-main: (defmethod assert-expr 'thrown? [message form] ...) — arg order [message form], dispatch on 2nd arg (Clojure-compatible).

test/clojure/core_test/portability.cljc (:phel branch, jank-lang#897) is written to the new [message form] contract. On v0.40.0 the namespaced p/thrown? defmethod never registers → [PHEL001] Cannot resolve symbol 'p/thrown?' → string/core tests fail to compile.

What

Pin phel-lang/phel-lang to dev-main (with minimum-stability: dev + prefer-stable: true) so the suite matches the nightly CI target instead of a stale stable tag.

Verification

$ composer test -- test/clojure/string_test/*.cljc
Passed: 79   Failed: 23   Error: 0   Total: 102

Compile errors gone. Remaining 23 failures are pre-existing type-strictness diffs (p/thrown? on nil/non-string — phel tolerates, Clojure JVM throws), not string-logic bugs.

Once a stable tag after v0.40.0 folds in the assert-expr change, this can revert to a ^0.4x pin.

v0.40.0 release predates the phel.test/assert-expr signature change
(arg order flipped to [message form], dispatch on 2nd arg) that the
suite's portability p/thrown? shim depends on, so the tag fails to
compile string/core tests. Pin dev-main to match the nightly CI target.
@Chemaclass Chemaclass self-assigned this May 29, 2026
@Chemaclass Chemaclass merged commit 4ebe1b7 into main May 29, 2026
4 checks passed
@Chemaclass Chemaclass deleted the chore/track-phel-dev-main branch May 29, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant