Misuse of debug names when debug names are disable
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- compilers
Research direction
Reproduce the issue with ForgeFlower 1.5.478.6 using the listed options, especially -udv=0, and compare the output with vanilla FernFlower using the linked Level diff. Trace how disabled debug names affect decompilation across classes; done means debug names no longer appear in output when that option is disabled.
Written by the indexing model from the issue text.
Description
When running ForgeFlower with -udv=0, debug names are showing up in the output. Here are the options I'm running with:
"-din=1", "-rbr=0", "-dgs=1", "-asc=1", "-hdc=0", "-rsy=1", "-iec=1", "-udv=0", "-jvn=1", "-log=WARN"
Here's a diff from vanilla FernFlower (build from a few days ago) and ForgeFlower 1.5.478.6 (06/13/20 10:44 PM):
@@ -96,17 +95,17 @@
private final BiomeManager biomeManager;
private final ResourceKey<Level> dimension;
private final ResourceKey<DimensionType> dimensionTypeKey;
protected Level(WritableLevelData var1, ResourceKey<Level> var2, ResourceKey<DimensionType> var3, DimensionType var4, Supplier<ProfilerFiller> var5, boolean var6, boolean var7, long var8) {
- this.profiler = var5;
- this.levelData = var1;
- this.dimensionType = var4;
- this.dimension = var2;
- this.dimensionTypeKey = var3;
- this.isClientSide = var6;
- if (var4.shrunk()) {
+ this.profiler = ☃;
+ this.levelData = ☃;
+ this.dimensionType = ☃;
+ this.dimension = ☃;
+ this.dimensionTypeKey = ☃;
+ this.isClientSide = ☃;
+ if (☃.shrunk()) {
this.worldBorder = new WorldBorder() {
public double getCenterX() {
return super.getCenterX() / 8.0D;
}
full diff of Level
This happens in every class
- Dominant language
- No language data
- Stars
- 110
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MinecraftForge/ForgeFlower
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MinecraftForge/ForgeFlower#131 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MinecraftForge/ForgeFlower#86 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MinecraftForge/ForgeFlower#85 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
All issues in MinecraftForge/ForgeFlower
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/eo#8869 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EricSpencer00/Resilient#4824 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/jeo-maven-plugin#1758 ·
-
generics
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
mlir
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
llvm/llvm-project#224908 · 1 comment ·