I have nothing much to add to this, besides my +1. Cheap precondition
tests should abort.
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel
Indeed, there's a reason why we still have fatal signals in modern
Unix/Linux. Some mistakes you can't back out of gracefully within the
scope of your already buggy program.
What we do have is a kernel that will clean up by killing just the
offending process in its entirety, and leaving a core
On 26/11/14 12:09, Alexandros Frantzis wrote:
> Hi all,
>
> in a recent review the subject of how to deal with precondition failures
> in the client API came up again. In discussions we had yesterday the
> consensus was that we should abort the process. This has the benefit of
> catching the error
Hi all,
in a recent review the subject of how to deal with precondition failures
in the client API came up again. In discussions we had yesterday the
consensus was that we should abort the process. This has the benefit of
catching the error as early as possible, making debugging much easier.
The
