wasi

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

When --cert-file and --private-key-file are set to the same file one overwrites the other and TLS fails with a parse error (which makes sense).

A quick check in the config that these parameters do not have the same value would be a useful addition I think.

If a new Environment is created, processes inside of it will not have access to any command line arguments or environment variables by default. They need to be added to the ConfigEnv struct from which the Environment is created. Currently this is only possible from the host, but is not exposed as a [host function

For future reference:
https://github.com/yonaskolb/XcodeGen
https://github.com/tuist/tuist/

We just see that people forget adding new demo files to the demo Xcode project, and this can and should be automated after all.

This issue is for tracking the overall progress of upstreaming our changes, please post here if you create any new PRs with our changes in the upstream repository:

• [stdlib] fix return type of getNumRuntimeFunctionCounters apple/swift#24182. Status: merged.
• [stdlib] Fix return type of swift_{uint64,int64,float*}ToString h

On blur, we should call this.xterm.scrollToBottom(). 😄