-
Notifications
You must be signed in to change notification settings - Fork 6
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
Clean up size_function semantics. #278
Conversation
7fa6bf2
to
d624dbc
Compare
Codecov Report
@@ Coverage Diff @@
## main #278 +/- ##
=======================================
Coverage 97.51% 97.51%
=======================================
Files 8 8
Lines 1410 1410
=======================================
Hits 1375 1375
Misses 35 35
Continue to review full report at Codecov.
|
d624dbc
to
50bbb53
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good - I like the documentation you've added. Just one question about always defaulting to "exponential" here, but maybe I'm missing something..
c9f5f3d
to
e78963e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. Reading through the thread, here's my suggestion:
- If start_size == end_size and no size function is specified, default to "constant"
- If start_size != end_size and size_function == "constant" raise an error
That is, hard equality rather than math.isclose. It's hard to imagine cases where the values would differ if the size function really was constant and it's not an error.
9901eab
to
c95d411
Compare
c95d411
to
433f9e2
Compare
Closes #262.