this `raises` mechanism is still used as a "trick" by the developers. Can it be
promoted as an official feature or external tool? ; meaning the compiler
supports some compilation switch (rough idea: as if someone added raises: [] to
all procs) that allows tracking the proc that raised the exception, and the
procs that call it but haven't captured it (allowed it to "bubble" up). a
harsher restriction can be to also require the developer to explicitly mark the
procs that raise exceptions. What do you think? it's a useful mechanism and a
good feature to prevent runtime crashes/bugs, but hard to use or more
accurately hard to find the origin of the issue, when just marking the main
proc as raises:[] .
