On 4/29/19, Russ Cox <r...@golang.org> wrote: > > Because assert() can be and is commonly misused, some programming language > theorists and designers look with disfavor on the whole idea of > assert(). For example, the Go programming language omits a built-in assert, > to eliminate its frequent misuse to mean ALWAYS. SQLite avoids this misuse > by reserving assert only for provable invariants and otherwise using ALWAYS > or NEVER. >
Please tell me if this is more fair and honest representation of this situation: Because assert() can be and is commonly misused, some programming language theorists and designers look with disfavor on the whole idea of assert(). For example, the Go programming language omits a built-in assert(), since the Go developers feel that the harm caused by misuse outweighs the benefit of having assert() as a built-in. The developers of SQLite disagree with that assessment. Indeed, the reason why this article exists is to push back against the notion that assert() is harmful. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
