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

I'd like to use this issue as a tracking issue for filling out gaps in wasmtime's introductory documentation. This includes our book (rendered), API documentation (rendered), and [examples](https://github.com/bytecodeallianc

As per the title.
By the way, thanks for the work you're doing on jphp, and sorry for so many issues, I'm really interested in the project, and would love to use it for lotsa cool magic upcoming stuff <3

Describe the Bug
I'm trying to create a completely static binary including inkwell however inkwell forces to always dynamically link to libffi with this line in build.rs

if cfg!(not(target_os = "windows")) {
    println!("cargo:rustc-link-lib=dylib=ffi");
}

llvm-sys works around this issue by introducing an environment variable: LLVM_SYS_{}_FFI_WORKAROUND, if declare

Sometimes when the code changes (e.g. when I update packages) there will be some problem that Revise doesn't know how to handle, so I get warnings of the form "Due to a previously reported error, the running code does not match saved version for the following files ..." with a list of files. Sometimes the files it's warning be about are for features I'm not using, so it would be great to have a wa

The ported markdown documentation attempts to glean technical documentation that is relevant to moonjit such as installation and execution instructions, API, etc. It does not have benchmark numbers, sponsorship acknowledgements or contact details since they are not relevant to moonjit.

In the process however, a number of cross-links have gone missing and the port also may have errors, formatti

Is your feature request related to a problem? Please describe.
If you have XAML Databinding to public members and use ForceRen (because lets assume your project is not a public library so renaming public methods is acceptable) then this will obviously break databinding.

Describe the solution you'd like
I've hacked a solution which extracts all databinding out of the XAML and makes a l