cplir-c
cplir-c
Alternatively, if the hardcoded space keybind was replaced with a keybinding option, it could be used to change the key from space to something else, or to no binding at...
Here's [where the keybinding is used currently](https://github.com/AppliedEnergistics/Applied-Energistics-2/blob/7623d3d7f7de39cc96b5b06e23a905ebc9b4667b/src/main/java/appeng/client/gui/me/common/MEStorageScreen.java#L251) the line: ```java if (InputConstants.isKeyDown(Minecraft.getInstance().getWindow().getWindow(), GLFW.GLFW_KEY_SPACE)) { ```
A less user-friendly but simpler solution could be to make list scanning operations add to the op limit? I was thinking it would be fun to make a hash table...
Could you sort by the position in the output of `wlr-randr | grep -P "Position|^[^ ]+"` or something? I figure you're probably unplugging & re-plugging in displays regularly.
When I've tried to get back into the same recipe tree, I can tell it's a new one because it always clears my tag selections.
Is this PR not being merged because it needs updating?
That's gradle complaining that your Java version is too new Looking at [this table](https://docs.oracle.com/javase/specs/jvms/se19/html/jvms-4.html#jvms-4.1), I think you were running Java 19. Java 17 or 18 might work instead?
How do we want to handle boxing and unboxing? I like to explicitly use Integer.valueOf and .intValue(), but I've also seen casting to Object and casting to int, or leaving...
Streams are probably fine until they're in a performance-critical area, then it should be benchmarked. I'll put them back in my PR. Unless they're not more readable than for loops?
We don't want to use `var` for Java 8 compat, right? Should we use this. instead of just ? Would it be the same for methods? I prefer using `this`...