Repository navigation
slang: regenerate against 2026.16 - #11
Merged
Merged
Conversation
Pinned natives, per-platform manifests, the extracted ABI model and lock, and the generated Java bindings, all regenerated from v2026.16 by .github/workflows/slang-bump.yml (run 32815010486). The append-only lock was enforced, not reset, so this is an additive ABI change. Extraction ran on macos-15 and cross-validated all six target triples. :slang:test ran against the new binaries on the four platforms ci.yml covers before this branch was pushed; windows-aarch64 and macos-x86_64 are published but untested, as they are today.
Contributor
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.1.3
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
Merged
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.
Regenerated from upstream
v2026.16by the Slang version bump workflow (run 32815010486), which pushed this branch only after all four test legs went green.What changed
natives/build.gradle.kts—slangVersion2026.14.1→2026.16, and all sixnatives/manifests/SHA-256 records re-recorded against the new release assets.SlangLibrary.PINNED_SLANG_VERSION→2026.16.api/slang-abi.lock/api/slang-api.json— enforced, not reset. The only ABI movement is additive: four newSlangLanguageVersionentries (SLANG_LANGUAGE_VERSION_202A= 2025,202B= 2026,202C= 2027,NEXT= 2027). No existing fact moved, so upstream held the append-only contract.Slang 2026.14.1→2026.16).SlangLanguageVersion.javais the sole generated file with real content changes.SLANG_LANGUAGE_VERSION_LATESTstill resolves to 2026, so nothing shifts semantically for existing callers; 2027 appears only as the newNEXT/202Caliases.Worth a look during review
The
202A/202B/202Cnames are upstream's own, and they alias values that already have spellings rather than introducing new ones. If the idiomatic layer should not surface all three, that is a follow-up rather than a change to this regeneration — this branch is byte-for-byte what the generator produced.Verification
Extraction ran on
macos-15and cross-validated all six target triples (DESIGN.md §3.4).:slang:testran against the new binaries on the four platformsci.ymlcovers;windows-aarch64andmacos-x86_64are published but untested, as they are today.Closes #10