Skip to content
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

any/all for building predicates on KLists #114

Merged
merged 3 commits into from
Dec 15, 2015

Conversation

eparejatobes
Copy link
Contributor

No description provided.

@eparejatobes
Copy link
Contributor Author

All this should be non-breaking, and included in 0.8.1.

@laughedelic
Copy link
Contributor

Nope, it should be 0.9.0:

  • Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
  • Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API.

http://semver.org

@eparejatobes
Copy link
Contributor Author

@laughedelic your carbon-based predicate evaluator has a bug 😛

@eparejatobes
Copy link
Contributor Author

do we need syntax for this? with what we have here in 8211fa7 the common use case would be

def doSomething[L <: AnyKList](l: L)(implicit
  p: all[isBlue] isTrueOn L
): L = l 

@eparejatobes
Copy link
Contributor Author

modulo syntax, LGTM

@laughedelic
Copy link
Contributor

I think no syntax is necessary for this

@eparejatobes
Copy link
Contributor Author

fine merging

@eparejatobes eparejatobes merged commit fd47efe into master Dec 15, 2015
@eparejatobes eparejatobes deleted the feature/any/all/klists branch December 15, 2015 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants