It might be possible to have a more efficient way to pipe a file to a stream by adding a .stream method to FileHandle.

e.g.

FileHandle.prototype.stream = async function (dst, { start = 0, end, signal } = {}) {
 // TODO: this[kRef](), this[kUnref](), if (signal.aborted) throw AbortError()
  let pos = start
  while (true) {
    if (end && pos >= end) {
      break
    }
  

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

• Source

JsPointerToString(NULL, 0, &str);

• Expected
  str = empty string

• Actual
  failed and returns JsErrorNullArgument

I think this should be possible

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

In the prototype implementation of value types support, the letter Q is used as a prefix in the bytecode for the signatures of classes that are value types, as distinguished from concrete identity type classes, interfaces and abstract classes, whose signatures are prefixed with the letter L.

Minimal changes to handle the Q prefix in the JIT compiler were merged into OpenJ9 in [pull reques

Tons of good improvements that can be made to the codebase:
https://deepsource.io/gh/elsaland/elsa/issues/?category=recommended

pelotom/runtypes#39 (comment)

const Foo = Union(
  // ...
).named('Foo');

We may need an API like this in order to get better error messages.

Add a dark/light mode switch in the menu.
The semantic-ui framework already handles that.
The thing is to also change the plot background color when in dark mode.