core.async

Compilation errors inside go block always reported as first line of block

Details

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

Description

I've noticed that when there are any errors inside a go block, the line number of the error is always the line containing the go symbol.

I suspect that some meta data on the forms that are converted into a state machine is being lost in the process.

This is quite annoying and quite leaky (in the abstraction sense). It makes it that much harder to track down the source of errors.

Activity

Hide
Timothy Baldridge added a comment -

Working on this, may be a few weeks out yet.

Show
Timothy Baldridge added a comment - Working on this, may be a few weeks out yet.
Hide
Hugo Duncan added a comment -

This effects both compilation errors and line numbers in stack trace frames.

Show
Hugo Duncan added a comment - This effects both compilation errors and line numbers in stack trace frames.
Hide
Timothy Baldridge added a comment -

Completed in CLJ, once we get a tools.analyzer.cljs I'll add this to CLJS as well.

Show
Timothy Baldridge added a comment - Completed in CLJ, once we get a tools.analyzer.cljs I'll add this to CLJS as well.

People

Vote (2)
Watch (2)

Dates

  • Created:
    Updated: