Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: swiftwasm/JavaScriptKit
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.44.0
Choose a base ref
...
head repository: swiftwasm/JavaScriptKit
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.44.1
Choose a head ref
  • 2 commits
  • 2 files changed
  • 3 contributors

Commits on Feb 13, 2026

  1. Prevent cross-module inlining of remaining @_extern(wasm) functions (#… 

    …631)

Extends the fix from b3ddd88 (which addressed f32/f64) to all remaining
public @_extern(wasm) BridgeJS intrinsics: i32, string, pointer, throw,
init_memory, and struct_cleanup.

Without @inline(never) wrappers, the Swift compiler can inline these
functions across module boundaries, causing the wasm import module
attribute to change from "bjs" to "env". This results in a wasm-ld
linker error when a downstream module (e.g. via BridgeJS codegen)
references the same symbol with a different import module.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
    @fjtrujy @claude
    fjtrujy and claude authored Feb 13, 2026
    Configuration menu
    Copy the full SHA
    bab0adb View commit details
    Browse the repository at this point in the history

  2. CI: Use debug builds for SwiftSyntax in ./Examples/Embedded (#632)

    @kateinoigakukun
    kateinoigakukun authored Feb 13, 2026
    Configuration menu
    Copy the full SHA
    d0c0282 View commit details
    Browse the repository at this point in the history
Loading