[Feature Request] Basic Constant Un-inlining

[ProdOrDev]

Currently when browsing through certain source files, such as com/mojang/blaze3d/vertex/Tesselator, you may encounter inlined constants, such as 786432 which refers to Tesselator.MAX_BYTES but was inlined during compilation.

It would be nice to have basic system that looks at the static final <primitive> FOO = ... declarations within a class and un-inlines them within the following method/field bodies of said class.

While this would not handle every case, especially cases when constants are inlined across classes, it would help with a decent majority (based on my own browsing experience).

[modmuss50]

Yes, this is planned. The big task to complete first is to have a way to provide the data, this will be using the unpick format that yarn previously used. It will then need intergrating into the source, ideally in a way that doesnt affect the line numbers.