Consider a more 'swifty' API about swift-overture

[stephencelis]

Ha, we actually made concat a lil more "swifty" in order to support trailing closures.

concat(buttonStyle) {
  $0.backgroundColor = .red
}

// vs.

concat(buttonStyle, and: {
  $0.backgroundColor = .red
})

This is a bit of a cheat code, but it works with concat as it scales to its variadic number of arguments.

concat(a, b, c, d, e, f, and: g)

The pipe and chain functions also are overloaded to create larger pipelines. I'm not sure what to do about scaling them, though:

pipe(a, into: b, then: c, before: d, andThen: e)

I'm also not sure if these kinds of labels are readable together. E.g., using with makes the meaning less clear:

with(x, pipe(incr, into: square))

I think in general the goal of these functions is to reduce visual noise and focus on the pipeline and composition. It should also be easy to manipulate existing pipelines and plug a new function into them anywhere, which is a flexibility that seems at odds with adding argument labels.

pipe(a, b, c, d, e)

We're up to discuss ideas that address these problems, though!

[jbarros35]

I'm using it just to say that's a huge achievement and work, I'm reading it and impress, do you had a Medium article about it?
That's a game change for Swift. I'm pretty sure that work will have recognition in the future when people would be aware of these workings.
By the way, if you allow me I want to contribute creating more test cases for improving your code coverage tests.
Thank you!

[gmosx]

Heh, you got me confused. I am also not sure what is the best API after all ;-)

[stephencelis]

Going to close this for now. Thanks for the discussion! Feel free to make suggestions for any other specific API changes by opening a new issue 😄