Skip to content
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

Add xform support to thaw #153

Closed
ptaoussanis opened this issue Jan 21, 2023 · 1 comment
Closed

Add xform support to thaw #153

ptaoussanis opened this issue Jan 21, 2023 · 1 comment
Assignees
Milestone

Comments

@ptaoussanis
Copy link
Member

Motivation: #152

This shouldn't be difficult to do, and may be generally useful?
Though would want to check the cost of adding an additional dynamic binding that most people wouldn't use.

@ptaoussanis ptaoussanis self-assigned this Jan 21, 2023
@ptaoussanis ptaoussanis added this to the v3.3 milestone Mar 20, 2023
@ptaoussanis ptaoussanis changed the title Consider adding xform support to thaw Add xform support to thaw Jul 31, 2023
@ptaoussanis
Copy link
Member Author

Closing, this will be addressed in forthcoming release 👍

ptaoussanis added a commit that referenced this issue Aug 2, 2023
Note: also considered (but ultimately rejected) idea of a separate
`*thaw-mapfn*` opt that operates directly on every `thaw-from-in!`
result.

This (transducer) approach is more flexible, and covers the most
common use cases just fine. Having both seems excessive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant