-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
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
extract_number does not directly handle multiple decimal places #88
Comments
Working fix, need to write tests and then I'll PR. |
Update: I've improved the fix to ensure that All that remains now is to communicate back up the chain to |
ChanceNCounter
added a commit
to ChanceNCounter/lingua-franca
that referenced
this issue
Mar 16, 2020
* extract_number(), extract_numbers(), and all helper functions gain a keyword parameter `decimal_places` (for helpers, just `places`) which does what it sounds like, using builtin round(). * avoid capturing non-adjacent numbers as decimal places * avoid capturing already-used decimal places as separate numbers in extract_numbers() * add a few tests for the above
This was referenced Mar 16, 2020
ChanceNCounter
added a commit
to ChanceNCounter/lingua-franca
that referenced
this issue
Mar 24, 2020
* extract_number(), extract_numbers(), and all helper functions gain a keyword parameter `decimal_places` (for helpers, just `places`) which does what it sounds like, using builtin round(). * avoid capturing non-adjacent numbers as decimal places * avoid capturing already-used decimal places as separate numbers in extract_numbers() * add a few tests for the above
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calling attention to this TODO.
I'm marking this as a bug because I think that's how users will perceive it, although one could argue that it's just unimplemented functionality.
The text was updated successfully, but these errors were encountered: