-
Notifications
You must be signed in to change notification settings - Fork 76
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
Expose RefinementProvider methods #1388
Expose RefinementProvider methods #1388
Conversation
I've seen similar flakiness in CI recently, looks like some nondeterminism in the compiler. Will retry |
did the trick :) |
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.
LGTM, any objections @Baccata ?
I think it's fine. Just a minor comment on the parameter name. |
Hmm, failed again on
|
that's a bit concerning 😸 |
It is useful to have access to these methods sometimes in more dynamic context, when for example
implicit def enumLengthConstraint[E <: Enumeration.Value]
cannot be invoked, due to constraints, but it is very easy to provide a size.EDIT: Weird, fails on
[aws-sandbox] (aws-sandbox / Compile / compileIncremental) Compilation failed
, it works locally, is it known to be flaky in CI for some reason?