On assertion naming (is VS check VS assert VS ...) Andrew Tropin (17 Apr 2026 12:57 UTC)
Re: On assertion naming (is VS check VS assert VS ...) Jakub T. Jankiewicz (17 Apr 2026 13:42 UTC)
Re: On assertion naming (is VS check VS assert VS ...) Marc Nieper-Wißkirchen (17 Apr 2026 13:55 UTC)
Re: On assertion naming (is VS check VS assert VS ...) Andrew Tropin (17 Apr 2026 14:20 UTC)
Re: On assertion naming (is VS check VS assert VS ...) Sudarshan S Chawathe (19 Apr 2026 20:13 UTC)

Re: On assertion naming (is VS check VS assert VS ...) Jakub T. Jankiewicz 17 Apr 2026 13:42 UTC


On Fri, 17 Apr 2026 19:56:53 +0700
Andrew Tropin <xxxxxx@trop.in> wrote:

> The most heated discussion so far was regarding assertion naming, `is`
> syntax in particular.

If name of "is" the most problematic. Let's make a compromise and make a
way to define it yourself.

e.g.:

(define is (make-....))

The user will be able to use whatever name he wants, and the spec can use
"is".

I could use:

(define t.is (make-...))

and someone else would be able to use check/assert or whatever he or she
prefers.

The name for the constructor function is up to you.

--
Jakub T. Jankiewicz, Senior Front-End Developer
https://jakub.jankiewicz.org
https://lips.js.org
https://snapp.md
https://koduj.org