We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The ChannelMode class' latter two comments (1, 2) are wrong.
An enum value with 0 adHocNetworkChannels and 0 cableCapacityFactor does not disable requirements, but rather limit the amount of used channels to 0.
See: with this setup and the following enum extension:
@Mixin(appeng.api.networking.pathing.ChannelMode.class) public class ChannelModeNoneEnumExtension { @Mutable @Shadow @Final private static appeng.api.networking.pathing.ChannelMode[] $VALUES; @Invoker(value = "<init>") private static appeng.api.networking.pathing.ChannelMode create(String name, int ordinal, int adHocNetworkChannels, int cableCapacityFactor){ throw new IllegalStateException(); } static { appeng.api.networking.pathing.ChannelMode NONE = create("NONE", $VALUES.length, 0, 0); $VALUES = ArrayUtils.add($VALUES, NONE); } }
I would correct this by simply removing the remark, since it's (clearly) not utilized.
The text was updated successfully, but these errors were encountered:
Fix #8022: Remove wrong documentation comments in ChannelMode
3a9ebba
I sure hope you aren't doing this kind of enum extension in production. 😄
Sorry, something went wrong.
0d3f023
They say ignorance is bliss, I hope you remain blissful on this matter.
No branches or pull requests
The ChannelMode class' latter two comments (1, 2) are wrong.
An enum value with 0 adHocNetworkChannels and 0 cableCapacityFactor does not disable requirements, but rather limit the amount of used channels to 0.
See:
with this setup
and the following enum extension:
I would correct this by simply removing the remark, since it's (clearly) not utilized.
The text was updated successfully, but these errors were encountered: