-
-
Notifications
You must be signed in to change notification settings - Fork 434
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
Move ks #1525
Move ks #1525
Conversation
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.
Thanks.
I'm not sure about depending on spfunc
; that appears not to have been touched in three years and has one open issue noting an inaccuracy.
Further note: could you split
(Optionally more segregation of tests.) Part of the rationale is to make it easier to use this for additional tests — I'd like to add some for weighted sampling (for which we have several variants, so better to use a separate file). |
I see the point, but before we just copy pasted their zeta implementation |
84ec3a9
to
3c89aae
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.
Why did you include distr_test/Cargo.lock.msrv
? I wasn't intending to run these tests on the MSRV, so this shouldn't be needed.
It thought I put them with the other tests, so they get run on every supported platform. This would also run the MSRV tests and it seems simpler letting it pass these than try to avoid running them. |
Aha. I don't think that's necessary — the value-stability tests are there to ensure that we get the same results everywhere. |
Good point. |
More exhaustive value-stability tests would be good, yes. It wouldn't surprise me if there are some FP issues we've missed somewhere. In fact, we probably have given that tests pass both with and without |
CHANGELOG.md
entrySummary
Motivation
#1519