Yes, it is supposed to do that correctly if you have the option turned on.
Robby
On Mon, Jun 1, 2015 at 3:50 PM, 'John Clements' via users-redirect
wrote:
>
>> On Jun 1, 2015, at 1:46 PM, Robby Findler
>> wrote:
>>
>> I think that if you don't have up to date .zo files, arbitrary badness
>> c
> On Jun 1, 2015, at 1:46 PM, Robby Findler wrote:
>
> I think that if you don't have up to date .zo files, arbitrary badness
> can ensue.
Just to check my development model; generally, when I’m working on multiple
interdependent libraries in a collection, my experience has been that if I make
I think that if you don't have up to date .zo files, arbitrary badness
can ensue.
Robby
On Mon, Jun 1, 2015 at 3:16 PM, Asumu Takikawa wrote:
> On 2015-06-01 12:50:33 -0700, 'John Clements' via users-redirect wrote:
>> Contract error: expected “text.rkt”, got #
>> from contract on gather-grades,
On 2015-06-01 12:50:33 -0700, 'John Clements' via users-redirect wrote:
> Contract error: expected “text.rkt”, got #
> from contract on gather-grades, with contract (“text.rkt” -> boolean?)
>
> … In other words, the “ClassInfo?” predicate had mysteriously been replaced
> by one that checked for th
I just got an interesting and very scary contract error. I tried to reproduce
it, but I can’t quite do it. I think I can see (part of) what’s going on,
though.
Suppose I have a file called bad1.rkt that is in Typed Racket (I’m guessing
this is significant) and exports a structure called ClassIn
5 matches
Mail list logo
