Skip to content
#

runtime

Here are 938 public repositories matching this topic...

marek-safar
marek-safar commented Jul 30, 2019

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
fitzgen
fitzgen commented Dec 11, 2020

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

good first issue fuzzing
bkolobara
bkolobara commented Aug 31, 2021

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

good first issue

Improve this page

Add a description, image, and links to the runtime topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the runtime topic, visit your repo's landing page and select "manage topics."

Learn more