Using a lambda in a floe position is likely to be a common syntax error in practice today (although I'm hard pressed to come up with an example where we really should be using a lambda rather than a flow, aside from wanting a different order of effects..). That would seem to support that we should allow this natural tendency by recognizing it as a shorthand way to escape to Racket. On the other hand, it could lull the user into a belief that they are writing expr syntax in this position rather than floe, which may cause confusion if they try to write other Racket forms without escaping them. I'm not too worried myself, but mentioning it in case anyone else has any thoughts on it.
This also removes an unused utility that I noticed was showing as uncovered by tests.
Public Domain Dedication
[x] In contributing, I relinquish any copyright claims on my contribution and freely release it into the public domain in the simple hope that it will provide value.
(Why: The freely released, copyright-free work in this repository represents an investment in a better way of doing things called attribution-based economics. Attribution-based economics is based on the simple idea that we gain more by giving more, not by holding on to things that, truly, we could only create because we, in our turn, received from others. As it turns out, an economic system based on attribution -- where those who give more are more empowered -- is significantly more efficient than capitalism while also being stable and fair (unlike capitalism, on both counts), giving it transformative power to elevate the human condition and address the problems that face us today along with a host of others that have been intractable since the beginning. You can help make this a reality by releasing your work in the same way -- freely into the public domain in the simple hope of providing value. Learn more about attribution-based economics at drym.org, tell your friends, do your part.)
Summary of Changes
We discussed this in last week's Qi meeting. A couple more thoughts:
Using a
lambdain afloeposition is likely to be a common syntax error in practice today (although I'm hard pressed to come up with an example where we really should be using a lambda rather than a flow, aside from wanting a different order of effects..). That would seem to support that we should allow this natural tendency by recognizing it as a shorthand way to escape to Racket. On the other hand, it could lull the user into a belief that they are writingexprsyntax in this position rather thanfloe, which may cause confusion if they try to write other Racket forms without escaping them. I'm not too worried myself, but mentioning it in case anyone else has any thoughts on it.This also removes an unused utility that I noticed was showing as uncovered by tests.
Public Domain Dedication
(Why: The freely released, copyright-free work in this repository represents an investment in a better way of doing things called attribution-based economics. Attribution-based economics is based on the simple idea that we gain more by giving more, not by holding on to things that, truly, we could only create because we, in our turn, received from others. As it turns out, an economic system based on attribution -- where those who give more are more empowered -- is significantly more efficient than capitalism while also being stable and fair (unlike capitalism, on both counts), giving it transformative power to elevate the human condition and address the problems that face us today along with a host of others that have been intractable since the beginning. You can help make this a reality by releasing your work in the same way -- freely into the public domain in the simple hope of providing value. Learn more about attribution-based economics at drym.org, tell your friends, do your part.)