[ASYNC-40] do not transform forms that have :no-transform metadata attached Created: 29/Nov/13 Updated: 05/May/14
Interaction between core.match clauses and the core.async transform is undesirable. core.async should respect some hook so that some forms are left alone. For example:
All code generated for [1 2] and [3 4] would have this metadata attached to it.
|Comment by Rich Hickey [ 30/Nov/13 9:25 AM ]|
Can you be more specific? This seems like a bad idea, and I wonder why it's desired.
|Comment by David Nolen [ 30/Nov/13 2:12 PM ]|
To show how bad the interaction is between core.async and a library like core.match that also generates a lot of code consider the following:
But if the user wraps this typical expression in a go block: