On Mon, Apr 29, 2019 at 3:28 PM Richard Hipp <d...@sqlite.org> wrote:
> On 4/29/19, Richard Hipp <d...@sqlite.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(), 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. > > > > Language similar to the above is now on the website. Your feedback is > appreciated. > This text and the text on the web site work for me. For what it's worth, it was not clear to me until just now that the article existed to push back on a general "asserts considered harmful" notion. I was reading it as primarily documenting SQLite coding conventions. The reference to Go makes more sense to me now. I also agree with all your comments about the benefits of invariant(x) when it is used properly. Thanks very much for a productive, enlightening discussion, and for making the changes. Best, Russ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
