5 Commits

Author	SHA1	Message	Date
Louis Gesbert	c01d4ac512	Fix exception positions being lost during translation/optimisations ... Positions within the Default terms are specially important since they can come from separate definitions in the source (before this, we would be falling back to the single declaration).	2024-04-30 17:56:06 +02:00
Louis Gesbert	9d07015864	Unify runtime error handling ... - Clearly distinguish Exceptions from Errors. The only catchable exception available in our AST is `EmptyError`, so the corresponding nodes are made less generic, and a node `FatalError` is added - Runtime errors are defined as a specific type in the OCaml runtime, with a carrier exception and printing functions. These are used throughout, and consistently by the interpreter. They always carry a position, that can be converted to be printed with the fancy compiler location printer, or in a simpler way from the backends. - All operators that might be subject to an error take a position as argument, in order to print an informative message without relying on backtraces from the backend	2024-04-26 18:31:26 +02:00
Louis Gesbert	090faf8c9f	Fix statement ordering in scalc	2024-04-23 16:01:23 +02:00
Louis Gesbert	8ae9701a4f	Fix python name clash printing again, for non-ascii	2024-04-05 15:25:46 +02:00
Louis Gesbert	f71db385d5	Python backend: workaround func/var name clash	2024-04-05 14:45:17 +02:00