Hello and happy new year,
Beside the ideal type inference of exception (availaible in several papers, in particular this one: https://www.researchgate.net/publication/269201496_Type-Based_Analysis_of_Uncaught_Exceptions),
I think a few simple things could help the programmer:
-
getting the complete list of exception that a program can raise together with the function of library name that uses them (there is probably a way to get this already, by examining the result of the compilation in dlambda ?)
-
getting a warning when you catch all exceptions and do not re-raise them (which is certainly an error because for instance of Out_of_memory or Stack_overflow). In the rare case you really want to do that (the top loop of your program), you can silent the exception.