core.async

do not transform forms that have :no-transform metadata attached

Details

  • Type: Enhancement Enhancement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

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:

(match [x y]
  [1 2] ...
  [3 4] ...)

All code generated for [1 2] and [3 4] would have this metadata attached to it.

Activity

David Nolen made changes -
Field Original Value New Value
Priority Major [ 3 ] Minor [ 4 ]
Assignee Rich Hickey [ richhickey ]
David Nolen made changes -
Description 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:

{code}
(match [x y]
  [1 2] ...
  [3 4] ...)
{code}

All code the for the match clauses would have this metadata attached to it.
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:

{code}
(match [x y]
  [1 2] ...
  [3 4] ...)
{code}

All code generated for {{[1 2]}} and {{[3 4]}} would have this metadata attached to it.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated: