Skip to content

Reorganize WASI-related files in Tools/wasm #133600

Closed

Description

@brettcannon

The files in Tools/wasm are a little messy as nearly all Emscripten-related files are in emscripten/ while the WASI-related files are not. So I want to:

  • Add a wasi/ directory and move code related to wasi.py there
  • Make wasi.py a deprecated shim for calling wasi/
  • Update CODEOWNERS such that @freakboy3742 isn't bothered about WASI-only stuff and I'm not bothered about Emscripten-only stuff

Linked PRs

Activity

  1. self-assigned this
    on May 7, 2025
  2. brettcannon commented on May 7, 2025

    @brettcannon
    MemberAuthor

    I have a PR ready to go into main and then to backport to 3.14, but main is currently broken for cross-builds (should be fixed by #133599).

  3. added 2 commits that reference this issue on May 7, 2025
  4. brettcannon commented on May 7, 2025

    @brettcannon
    MemberAuthor

    ee49644 was an accidental preview of the PR. 😅

  5. brettcannon commented on May 7, 2025

    @brettcannon
    MemberAuthor

    @freakboy3742 the decision was made on Discord that it was better to just leave my mistake commit, so in classic EAFP tradition I'm asking if you have any feedback on the changes I made and anything you want me to change.

  6. freakboy3742 commented on May 7, 2025

    @freakboy3742
    Contributor

    @brettcannon I think that all makes sense to me.

    The only bigger picture question I've got is around the use of the Tools directory - I appreciate there's history and backwards compatibility issues, but if we're doing a re-org anyway, does it make any sense to promote wasm to a top-level folder in the repo, similar to every other supported platform?

  7. brettcannon commented on May 8, 2025

    @brettcannon
    MemberAuthor

    if we're doing a re-org anyway, does it make any sense to promote wasm to a top-level folder in the repo, similar to every other supported platform?

    Possibly. I think that's a bigger question for the overall core team (something you want to bring up at the language summit?).

  8. brettcannon commented on May 8, 2025

    @brettcannon
    MemberAuthor

    BTW I left the config.site file in place for Emscripten as I wasn't sure if you wanted to move it into the emscripten/ directory or not.

  9. freakboy3742 commented on May 8, 2025

    @freakboy3742
    Contributor

    if we're doing a re-org anyway, does it make any sense to promote wasm to a top-level folder in the repo, similar to every other supported platform?

    Possibly. I think that's a bigger question for the overall core team (something you want to bring up at the language summit?).

    I already have a slide for this (in the context of support for other Apple platforms). 😄

  10. 4 remaining items

  11. added 2 commits that reference this issue on Jun 25, 2025
  12. added a commit that references this issue on Jul 12, 2025
  13. added a commit that references this issue on Jul 21, 2025
  14. added a commit that references this issue on Jul 21, 2025
  15. added a commit that references this issue on Jul 21, 2025
  16. added a commit that references this issue on Jul 22, 2025
  17. added a commit that references this issue on Aug 4, 2025
  18. added a commit that references this issue on Aug 19, 2025
  19. added a commit that references this issue on Sep 9, 2025
  20. added a commit that references this issue on Nov 3, 2025
  21. added a commit that references this issue on Nov 3, 2025
  22. added a commit that references this issue on Nov 3, 2025
  23. added a commit that references this issue on Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

3.14bugs and security fixes3.15bugs and security fixesOS-wasitype-refactorCode refactoring (with no changes in behavior)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions