You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into this while working on a project using coordinates. While I would like the minimum length of 5, it should apply to either side of the decimal.
So taking the example from #1109 I find 1000.01 more readable than 1_000.01 or 10.0003 more readable than 10.000_3
Maybe even be able to ignore after the decimal.
Is this something others would be interested in as well? Because then I'd look into making a PR.
The text was updated successfully, but these errors were encountered:
I just realized while looking at the code that this is actually how it works. This is an oversight/a case of the mondays.
I have another idea, and please tell me if this is not really useful or too specific. I'm also not entirely sure on the naming/api.
But let's say I want to have a minimum length of 5 for everything before decimal, so as #1109 suggests: 10000 becomes 10_000 but 1000 stays the same. But at the same time I want my decimals to be split at a later point. So my code could look like this:
I ran into this while working on a project using coordinates. While I would like the minimum length of 5, it should apply to either side of the decimal.
So taking the example from #1109 I find
1000.01
more readable than1_000.01
or10.0003
more readable than10.000_3
Maybe even be able to ignore after the decimal.
Is this something others would be interested in as well? Because then I'd look into making a PR.
The text was updated successfully, but these errors were encountered: