On Thu, Dec 1, 2016 at 7:29 PM, David Storrs wrote:
> I'm having trouble understanding the docs on hash contracts (
> https://docs.racket-lang.org/reference/data-structure-
> contracts.html#%28def._%28%28lib._racket%2Fcontract%
> 2Fprivate%2Fhash..rkt%29._hash%2Fc%29%29)
>
> What I'm trying to ex
On Thu, Dec 1, 2016 at 10:18 PM, Alexis King wrote:
> > On Dec 1, 2016, at 21:43, David Storrs wrote:
> >
> > The difference between a dictionary and a structure being that
> dictionaries are easily extensible on the fly and structures are not? I'm
> curious -- what are the elements of that des
> On Dec 1, 2016, at 21:43, David Storrs wrote:
>
> The difference between a dictionary and a structure being that dictionaries
> are easily extensible on the fly and structures are not? I'm curious -- what
> are the elements of that design and what are the reasons? It seems like a
> natural
On Thu, Dec 1, 2016 at 8:59 PM, Alexis King wrote:
> > On Dec 1, 2016, at 16:29, David Storrs wrote:
> >
> > - This function returns #t because it is a simple test function intended
> to get the hang of hash contracts...
> > - This function takes one argument...
> > - Which is a hash...
> > - Wh
> On Dec 1, 2016, at 16:29, David Storrs wrote:
>
> - This function returns #t because it is a simple test function intended to
> get the hang of hash contracts...
> - This function takes one argument...
> - Which is a hash...
> - Which has keys 'success, 'file-id, 'scratchdir-path, and 'chunk-h
5 matches
Mail list logo
