core.async

It is odd that the thread macro does not maintain per-thread bindings, the way the go macro does

Details

  • Type: Defect Defect
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Completed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

As stated, it is odd that thread and go are dissimilar in this way; if there's a rationale for it, I'd prefer to see it documented; otherwise, it would be nice to see thread do what go does.

Activity

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: