lift goes up to 11!

[ivanov]

I got a good laugh out of "lift should go up to 11" at the hackathon in
SF, so decided to submit a PR with the feature

[evancz]

Nice :D

Based on the thought process this PR kicked off and other stuff from that meeting, the current plan is as follows:

Core library has Signal.map all the way up to Signal.map5. At that point we'll start recommending (<~) and (~) if you really must go higher.

Part of the logic here is that I don't know of legitimate use cases for N > 5 at this point and we have a safety valve for people who find themselves in that spot. Furthermore, it makes the operators more of a realistic utility instead of a pretty extra.

[evancz]

Nice :D

Based on the thought process this PR kicked off and other stuff from that meeting, the current plan is as follows:

Core library has Signal.map all the way up to Signal.map5. At that point we'll start recommending (<~) and (~) if you really must go higher.

Part of the logic here is that I don't know of legitimate use cases for N > 5 at this point and we have a safety valve for people who find themselves in that spot. Furthermore, it makes the operators more of a realistic utility instead of a pretty extra.

[salutis]

Do we even need Signal.mapX functions? Wouldn't map, (<~), and (~) be enough?

[salutis]

Do we even need Signal.mapX functions? Wouldn't map, (<~), and (~) be enough?

[evancz]

Having talked to lots of beginners, many people struggle with (<~) and (~) for a while at first. I think it's valuable as an education tool at least, but I personally use mapN all the time.

[evancz]

Having talked to lots of beginners, many people struggle with (<~) and (~) for a while at first. I think it's valuable as an education tool at least, but I personally use mapN all the time.