Your formatting misses the structure from #55:

open type for categories:

Behavior

Undefined

Implementation

Machine

Integer

Overflow

Div_by_zero

Cast

Type_mismatch (bug)

Race

Array

Out_of_bounds of int*int

I assume we want to reflect the structure in the type (or some value) to be able to easily filter whole groups.
There are open questions:

do we want it flat and unqualified with polymorphic variants or do we want normal variants which might not be as convenient to write but are possibly safer?
do we want the type definition in one place or distributed with extensible variants (does not work with polymorphic variants)?

Untested and not all combinations, but should give some idea:

Extensible variants:
e.g. messages.ml:

type group = ..
let is_integer_error = function Integer _ -> true | _ -> false

e.g. intDomain.ml:

type integer_error = Overflow | Div_by_zero
type Messages.group += Integer of integer_error

e.g. base.ml:

open Messages
(* ... *)
warn `Must (Integer IntDomain.Div_by_zero) "..."

Normal variants all in one place:
e.g. messages.ml:

type integer_error = Overflow | Div_by_zero
type group = Integer of integer_error (* | ... *)
let is_integer_error = function Integer _ -> true | _ -> false

e.g. base.ml:

open Messages
(* ... *)
warn `Must (Integer Div_by_zero) "..."

Flat polymorphic variants:
e.g. messages.ml:

let is_integer_error = function `Overflow | `Div_by_zero -> true | _ -> false

e.g. base.ml:

(* ... *)
Messages.warn `Must `Div_by_zero "..."

Rework system outputting warnings #201

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions