-
Notifications
You must be signed in to change notification settings - Fork 105
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
Feature request: transform-exactly-one #172
Comments
I assume this is as efficient as it can be?
|
Your implementation will be more efficient by using |
Updated code
|
Thought about it and decided not to add this to Specter. From my experience I just don't see it being that valuable, and adding it could create confusion among some users (e.g. "Do I have to use transform-one! if it only touches one element?" or "Is it faster to use transform-one! over transform if it only touches one element?") |
During enhancement of the system, it is easy to forget some places where changes are needed.
I use transform a lot, however, maybe I forgot to update the path.
Having a transform-one!, which similar to select-one! would throw an exception if no changes, or too many changes are made, would be helpful.
The text was updated successfully, but these errors were encountered: