> Using exceptions for panics (go, rust) is a different and mostly unrelated / > orthogonal topic - here, they're not part of the "normal" code flow that > programmers use in their day-to-day prose, and if they were turned into quit > without unwinding, no significant/intended functionality is lost - exceptions > or not at this stage is an implementation detail.
The go and rust folks calling this an implementation detail is a pretty transparently political choice on their part. They say that because exceptions are unpopular, and because if most people use error codes then it's /more likely/ that programs will continue to work if unwinding just terminates. If it was actually an implementation detail then there would be no reason to support unwinding the stack at all. If anyone /ever/ uses the ability to halt unwinding then it's no longer an implementation detail.
