Zbigniew Jędrzejewski-Szmek 04499a70fb Drop the text argument from assert_not_reached() ... In general we almost never hit those asserts in production code, so users see them very rarely, if ever. But either way, we just need something that users can pass to the developers. We have quite a few of those asserts, and some have fairly nice messages, but many are like "WTF?" or "???" or "unexpected something". The error that is printed includes the file location, and function name. In almost all functions there's at most one assert, so the function name alone is enough to identify the failure for a developer. So we don't get much extra from the message, and we might just as well drop them. Dropping them makes our code a tiny bit smaller, and most importantly, improves development experience by making it easy to insert such an assert in the code without thinking how to phrase the argument.		2021-08-03 10:05:10 +02:00
..
sysusers.c	Drop the text argument from assert_not_reached()	2021-08-03 10:05:10 +02:00