diagnostic

type ColorMode ¶

type ColorMode int

ColorMode controls when ANSI color codes are used.

const (
	ColorAuto   ColorMode = iota // detect based on terminal and NO_COLOR
	ColorAlways                  // always use colors
	ColorNever                   // never use colors
)

type Diagnostic ¶

type Diagnostic struct {
	Severity Severity
	Message  string
	Spans    []Span
	Notes    []string // "= note:" lines (stack trace frames, etc.)
}

Diagnostic represents a single error, warning, or note with optional source annotations and trailing notes.

type Renderer ¶

type Renderer struct {
	// Color controls ANSI color output. Default is ColorAuto.
	Color ColorMode

	// SourceReader reads source file contents. If nil, os.ReadFile is used.
	SourceReader func(string) ([]byte, error)
}

Renderer formats diagnostics as Rust-style annotated source snippets.

func (r *Renderer) Render(w io.Writer, d Diagnostic) error

func (r *Renderer) RenderAll(w io.Writer, diags []Diagnostic) error

type Severity ¶

type Severity int

Severity indicates the severity level of a diagnostic.

const (
	SeverityError Severity = iota
	SeverityWarning
	SeverityNote
)

func (s Severity) String() string

type Span ¶

type Span struct {
	File   string // path for reading source; display name if unreadable
	Line   int    // 1-based line number
	Col    int    // 1-based start byte column
	EndCol int    // 1-based end byte column, INCLUSIVE (0 = auto-detect from source)
	Label  string // text shown under the underline
}

Span identifies a region of source code to highlight in the diagnostic.

UNITS AND CONVENTION. Col and EndCol are 1-based BYTE columns, and EndCol is INCLUSIVE -- it names the column of the span's last byte, not the one after it. A span covering "false" at columns 7 through 11 is Col: 7, EndCol: 11.

That is the OPPOSITE of parser/token.Location.EndCol, which is documented (as of the #463 fix) as an EXCLUSIVE byte column. The two types have same-named fields with opposite conventions, and nothing in the tree bridges one into the other today: cmd/diagnostic.go and repl/diagnostic.go both set Col and leave EndCol zero for auto-detection. The first caller to wire an analyser's end position straight into a Span would get an underline one caret too long, which is why the convention is written down here rather than left to be inferred (issue #469). Converting is `EndCol: loc.EndCol - 1`.

The RENDERER measures the underline in terminal CELLS rather than in bytes, so the carets line up with what a terminal draws even when the span holds multi-byte, East Asian wide, or combining characters -- see displayWidth in renderer.go. The byte convention here is about how a caller ADDRESSES the source; it is not the unit the carets are counted in.