Skip to content

Conversation

@DogeisCut
Copy link
Contributor

Resolves: #2328

Results:
10^33: 1Dc
10^36: 1 UDc
10^45: 1 QaDc
10^48: 1 QnDc

See https://pastebin.com/JpUFnLtp for full results, please let me know if you see anything wrong as I can not locate the resource I was previously using to verify this.

DogeisCut and others added 10 commits March 16, 2025 07:22
- Fixed the comment ID to match the extension ID.
- Structured long arrays in format function vertically for consistency.
- Re-ordered placement of extension (I recall being told not to worry about this?)
wow im glad this completley undid the vertical consistency you asked me to do.......
Resolves: TurboWarp#2328

Results:
10^33: 1Dc
10^36: 1 UDc
10^45: 1 QaDc
10^48: 1 QnDc

See https://pastebin.com/JpUFnLtp for full results, please let me know if you see anything wrong as I can not locate the resource I was previously using to verify this.
@github-actions github-actions bot added the pr: change existing extension Pull requests that change an existing extension label Nov 18, 2025
PPPDUD
PPPDUD previously requested changes Nov 18, 2025
Copy link
Member

@PPPDUD PPPDUD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I tested all modified functionality and found no bugs or unintuitive behavior.
  • I believe a well-formed project using an older version of this extension will not be broken by this new version.
  • I have no additional concerns.

You should assign the corrected block to a different opcode so that it doesn't break old projects reliant on broken behavior.

@GarboMuffin
Copy link
Member

Projects relying on clearly broken behavior are not "well-formed"

@DogeisCut
Copy link
Contributor Author

DogeisCut commented Nov 18, 2025

Projects relying on clearly broken behavior are not "well-formed"

I concur, which is precisely why I didn't make a new block for the fix.

@PPPDUD
Copy link
Member

PPPDUD commented Nov 18, 2025

Projects relying on clearly broken behavior are not "well-formed"

Fair. I'm still witholding my approval, but I don't object to someone else approving it and merging.

Copy link
Member

@GarboMuffin GarboMuffin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I tested all modified functionality and found no bugs or unintuitive behavior.
  • I believe a well-formed project using an older version of this extension will not be broken by this new version.
  • I have no additional concerns.

Copy link
Member

@CubesterYT CubesterYT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I tested all modified functionality and found no bugs or unintuitive behavior.
  • I believe a well-formed project using an older version of this extension will not be broken by this new version.
  • I have no additional concerns.

@GarboMuffin GarboMuffin changed the title Format Numbers: Resolve AD notation inconsistencies. DogeisCut/FormatNumbers: Resolve AD notation inconsistencies. Nov 18, 2025
@GarboMuffin GarboMuffin changed the title DogeisCut/FormatNumbers: Resolve AD notation inconsistencies. DogeisCut/FormatNumbers: Resolve AD notation inconsistencies Nov 18, 2025
@CubesterYT CubesterYT dismissed PPPDUD’s stale review November 18, 2025 23:59

"Fair. I'm still witholding my approval, but I don't object to someone else approving it and merging."

Going to need to dismiss to merge

@CubesterYT CubesterYT merged commit 8dde292 into TurboWarp:master Nov 19, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: change existing extension Pull requests that change an existing extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AD notation for "Format Numbers" extension is inaccurate.

6 participants