Chen Liang

For @nallar: imo the tool will be more bytecode oriented. the source-code generation part can just generate some pseudocode, as unlike in other projects where source code is used to...

Imo the patches will be bytecode oriented (like tiny mapping format, using bytecode parameter index than source-code method parameter index). It just need to have a simple way to convert...

So a quick summary here: We have backend (i.e. storage format that applies changes to bytecode/source) and compiler (convert dev-time format to backend) Mixin: - compiler: java-annotated classes, annotation processor...

Looking at https://github.com/eclipse/org.aspectj I believe aspectj is outdated (stays on Java 9!) and poorly documented; it is probably even less suitable than mixin

> I do want to enable preview features (would allow records if it is java 15) at runtime but allow modders to opt-into them if they wish. I dont see...

hmm, can we actually enable preview after a jvm starts (beside calling native stuff)? If we do add it, will it be a command line argument for launcher to add?

In addition, we have #40, where we think about putting code into modules. Imo we can make a custom module finder that reports minecraft code as one module, possibly an...

We haven't encountered actual records in minecraft code yet. Maybe this can serve as a tracking issue.

Yes, they are probably compiling with source compatibility 8 and target compatibility 16 (where there are nest mates, indy string concat, etc).

> It still wouldn't solve the case where a 3rd party mod is changing the game by e.g. making java 8 run java 16 mods. The mods wouldn't anticipate this...