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).

ee49644 was an accidental preview of the PR. 😅

@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.

@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?

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?).

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.

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). 😄