-
-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated methods CSV doesn't support record method names #922
Comments
The record field accessor methods are likely marked as synthetic by the compiler, which likely means they should not even be in the decompile. Are you trying to reflect them at runtime and hitting an error, or is it a "they seem to be missing"? Because I would generally expect them to be missing. Note that at runtime deobf, they probably deobf to their field name because they're synthetic. |
Runtime deobf doesn't work at all because the default modlauncher naming service loads its method mappings from All the required method names are already present in the SRG input of |
To make this clear, it has nothing to do with things being synthetic or not. This is a bug in FML, or at least a misunderstanding of design. The fix would be to update FML's Naming Service, but it can also be fixed on our end by duplicating the data into both csv files. So feel free to PR FG to add "f_" to the list of methods so it's retroactive. |
Fixing name service is quite doable. We'd need to identify the special case where the method is a field name somehow.. |
The point is they shouldn't be special cased. It'd just need to load both the methods and fields csv into a single dictionary. |
Currently, the generator for method and field CSV files,
OfficialChannelProvider
, distinguishes methods and fields by their prefix, which isfunc_
/m_
for methods andfield_
/f_
for fields. However, in records, the names of accessor methods are the same as the field they're accessing. As an example, see NoiseGeneratorSettings.surfaceRule.ForgeGradle/src/mcp/java/net/minecraftforge/gradle/mcp/OfficialChannelProvider.java
Lines 99 to 108 in 651e43f
This leads to all record method names being filtered out as fields by the generator.
When the mappings are later used at runtime by modlauncher for remapping class member names, record methods will never be remapped due to this issue.
The text was updated successfully, but these errors were encountered: