Closed Tyler-Yocolano closed 3 years ago
Meh... not sure. The main reason why they don't leave the item on the stack is symmetry with define and quote-define really...
I know that in some situations you'd like to keep the item on the stack to avoid repeating the variable but... is it worth changing the semantics of these operators? Is it more a more frequent use case, also for define and quote-define?
Closing, not implementing for now.
What are your thoughts on letting bind (@) and quote-bind (#) put their values on top of the stack?
For example, I have this code:
and I thought it might look and feel better as:
(scores swap counter succ @counter swap dset) map
Another simpler example is: