I use often array
in my project. I just realize that for an out of bounds
error in an assignment (e.g. a.(100) <- 5
), if there is no catching exception, it will silently stop the execution.
I would like to know the place where the error is raised, once every error like occurs. One way to do it is to add try ... with ...
around array operations, but obviously it is tedious and not good-looking...
Does anyone have a better idea?
Same logic for map
operations. I notice that for find
in map
, if no binding exists, Not_found
is raised, but if there is no try ... with ...
, nothing will be explicitly shown. How can I make it explicitly shown systematically?