0.0.1 alpha 2#5
Open
KotlinIsland wants to merge 27 commits into
Open
Conversation
KotlinIsland
force-pushed
the
0.0.1-alpha-2
branch
from
2f7e9d3 to
5cbe802
Compare
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
the transpiler emits PEP 695/696/646 syntax whose runtime floor is 3.13; running on the host's system python (3.10-3.12 on CI) made checker-clean blocks fail to parse. provision a fixed interpreter via uv instead Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
the postfix-`^` (propagate) reading of a glued `^` before a unary sign only makes sense in basedpython; in .py mode `a^-b` is plain `a ^ (-b)`. gating it on is_basedpython stops valid python becoming a parse error, which the formatter ecosystem check counts as an input syntax error Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
an f-string conversion (`f"{a if b else c!s}"`) lands on the conditional's
`else` tail; that position dropped the IN_INTERPOLATION flag, so the `!` was
eaten as the basedpython postfix force-unwrap and valid python became a parse
error. this tipped the formatter ecosystem check past its 3-error budget
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
it drives a python subprocess whose interpreter discovery and stdout encoding differ from unix; the checker/runtime contract it validates is platform independent, so linux + macos coverage suffices. every other test the PR adds is pure-rust and already green on macos, so this is the only windows-specific failure Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`based_round_trip` emits the platform line ending, so the multi-line case produced CRLF on windows while the test compared against the LF input. normalise the expected value the same way the other round-trip tests do Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
it spawns ~200 transpile+python subprocess pairs and provisions a python via uv on the first cold run, so it legitimately runs past the ci profile's 60s deadlock stop-gap and was being killed mid-run on linux Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
with the divergence harness now passing (rather than being killed at 60s), the linux job runs its whole pipeline — tests + doctests + dogfood + docs — which needs more than the upstream 20m budget on the slower fork runner 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.
a: 1 + 1 = 2dynamic'keyword' instead ofAnyawaitkeyword as attributefinal