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

Fix expression transform to conform to transform interface #1198

Merged
merged 2 commits into from
Jan 3, 2021

Conversation

mbj
Copy link
Owner

@mbj mbj commented Jan 3, 2021

  • This is a typical case where a type system would never let me go.
  • And a case where mutation testing in Ruby could not even force the
    Left here as there are no types (yet) for mutant to discover this
    case.

* This is a typical case where a type system would never let me go.
* And a case where mutation testing in Ruby could not even force the
  `Left` here as there are no types (yet) for mutant to discover this
  case.
@@ -26,7 +26,9 @@ class Config

DEFAULT = new(Hash[anima.attribute_names.map { |name| [name, []] }])

expression = ->(input) { Mutant::Config::DEFAULT.expression_parser.call(input) }
expression = Transform::Block.capture(:expression) do |input|
Mutant::Config::DEFAULT.expression_parser.call(input)
Copy link
Owner Author

@mbj mbj Jan 3, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want function composition as a syntax feature so badly. Miss you:

Data.Function.`.`

@mbj mbj merged commit a182c4f into master Jan 3, 2021
@mbj mbj deleted the fix/expression-parser branch January 3, 2021 03:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant