On Mon, Apr 29, 2019 at 9:49 PM Russ Cox <r...@golang.org> wrote: > On Mon, Apr 29, 2019 at 3:28 PM Richard Hipp <d...@sqlite.org> wrote: > 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. >
Very interesting discussion between two of my very favorite programmers. Thanks. (programmer here in the very general sense of developer, architect, designer, even perhaps "code-artist") I also agree with all your comments about the benefits of invariant(x) when > it is used properly. > I have no business being in this discussion between giants... But I also regret the lack of invariant/always/never (I dare not say assert...) in Go. I wish Robert/Rob/Ken/Russ instead of shunning "assertions" would promote "proper use" of invariant/always/never by making them a built-in part of the language, and have the compiler perform the kind of static analysis Richard mentions in this thread. My $0.02. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
