📗 API Reference Docs Problem

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

When I passed NaN and an object with the "valueOf" attribute value as a callable function to the first and second parameters of Math.max, chakra did not execute this function. According to the ES10 standard, the ToNumber operation is performed on each parameter of Math.max, and the "valueOf" attribute value function of the second parameter will be executed.

version

chakra-1_11_22

**co

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

There are a number of places in the JIT guarded with TR::Compiler->cls.classesOnHeap(). This query is hardcoded to always return true. J9 classes have resided on the heap for many years now and this is unlikely to change. I doubt this flexibility is still needed.

Assume TR::Compiler->cls.classesOnHeap() is always true and fold and remove code as necessary.

Leave the `classesOnHeap

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

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.