---
There was some talk of supporting arbitrarily large integers. This was
mostly an academic discussion, since the currently supported range
(64 bits) should cover all use cases.
On Wed, Dec 1, 2021 at 8:49 PM Paul Smith wrote:
>
> allowing practicality to drive simplification in code turns
On December 2, 2021 4:20 AM, Boris Kolpackov
> rsbec...@nexbridge.com writes:
>
> > Sadly, the import restrictions do not distinguish between message
> > digests and cryptography [...]
>
> You seem to be quite knowledgeable on the matter so can you provide one
> concrete example of where one
On December 2, 2021 3:44 AM, Edward Welbourne
> > My first counter-argument comes from the "$(shell git hash-object obj)"
> > suggestion which begs the question: if git, which relies heavily upon
> > SHA-1, is available, doesn't that mean SHA-1 is also natively
> > available? I'm not aware of git
rsbec...@nexbridge.com writes:
> Sadly, the import restrictions do not distinguish between message
> digests and cryptography [...]
You seem to be quite knowledgeable on the matter so can you provide
one concrete example of where one jurisdiction restricts export to
another of, say, an SHA-1
> My first counter-argument comes from the "$(shell git hash-object obj)"
> suggestion which begs the question: if git, which relies heavily upon SHA-1,
> is available, doesn't that mean SHA-1 is also natively available? I'm not
> aware of git being restricted in any jurisdictions.
Seems
