-
Notifications
You must be signed in to change notification settings - Fork 31
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
multiple value return error when using pipe operators #60
Comments
Thanks for trying Rash!
Yes, currently pipelines expect a single return value. I've
considered changing it to accept multiple values and automatically
convert it to a list, but I'm hesitant to do that.
You can use `call-with-values` to turn multiple values into a list
instead, or there are a couple of modules that export a `values->list`
macro that makes this more convenient (eg. br/list has one). Does
that work for you?
|
Or better stated, it is easy to make a custom pipeline operator macro that supports multiple values, but that wouldn't bring support to every operator. Are there compelling reasons you want to use multiple values in pipelines where converting them to a list in the function you use or using a multiple values operator doesn't work or is inconvenient? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was just playing with rash and noticed the following:
It fails similarly when using
|>>
as well.The text was updated successfully, but these errors were encountered: