Replace "crypto" with "entropic" Peter McGoron (05 May 2026 05:45 UTC)
Re: Replace "crypto" with "entropic" John Cowan (05 May 2026 06:15 UTC)
Re: Replace "crypto" with "entropic" Wolfgang Corcoran-Mathe (06 May 2026 23:57 UTC)
Re: Replace "crypto" with "entropic" Peter McGoron (07 May 2026 12:11 UTC)
Re: Replace "crypto" with "entropic" John Cowan (07 May 2026 23:43 UTC)
Re: Replace "crypto" with "entropic" Ray Dillinger (15 May 2026 07:08 UTC)

Re: Replace "crypto" with "entropic" John Cowan 05 May 2026 06:15 UTC

Both conventions are in use: see SRFIs 115 and 160.

On Tue, May 5, 2026 at 1:45 AM Peter McGoron <xxxxxx@mcgoron.com> wrote:
>
> This has the following benefits:
>
> 1. More in-line with system calls like `getentropy`.
> 2. More neutral. "Cryptographic" is a loaded term that people inevitably
> associate with "high quality," when there is little that a Scheme
> implementation can do to ensure that.
> 3. Emphasizes that the particular generator is not meant to be
> predictable. (CSPRNGs are repeatable and "cryptographic".)
> 4. Doesn't require you to define "cryptographic" in the SRFI.
>
> ____________________________________
>
> As an aside, the usual R7RS library convention is `(srfi 271
> [sublibrary])` not `(srfi 271 [library name] [sublibrary])`. I very much
> like the shortened convention over the SRFI 97 convention because then I
> don't have to remember the SRFI library name.
>
> -- Peter McGoron