jit

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

For now, Object protocol methods are (mostly) thin wrapper of matching vm functions. Because we don't need to have duplicated functions for same features, they need to be moved from vm to object protocol functions.

• vm path: vm/src/vm.rs
• object protocol path: vm/src/protocol/object.rs

The matching vm functions are easy to find because object methods are calling it.

• get_att

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

Current, if we try to run a more recent Java class in an old JVM, we get the following error message:

Error: LinkageError occurred while loading main class some.Class
	java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=some/Class, offset=6

However, it is not so easily to detect that the class was compiled with a version above the supported by the JVM.Hotspot

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

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

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