Skip to content

Conversation

@wildthink
Copy link

If you like this approach, I'll fully document it for a formal pull request.
I have some questions/ideas about it could be fully integrated into the Parser, etc.

Copy link
Owner

@NeedleInAJayStack NeedleInAJayStack left a comment

Choose a reason for hiding this comment

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

Hey sorry about the delay in review. This is awesome! Thanks!

I see you've added % into the unit system. I think that might be all we need for the parser to work correctly, but it may not use the correct +/- arithmetic. Could we add a test to validate its behavior?

Thanks again!

@wildthink
Copy link
Author

You were right (it appears :-) ), adding in the Percent as you suggested makes the parser happy and I updated the Expression solver correctly -- at least my tests pass :-)

@wildthink wildthink marked this pull request as ready for review September 14, 2025 02:08
Copy link
Owner

@NeedleInAJayStack NeedleInAJayStack left a comment

Choose a reason for hiding this comment

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

Thanks again @wildthink

@NeedleInAJayStack NeedleInAJayStack merged commit 78ffb04 into NeedleInAJayStack:main Sep 19, 2025
7 checks passed
@wildthink wildthink deleted the percent branch September 26, 2025 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants