It is a note from the contract system to itself to help track down places
that should be improved. Please feel free to ignore it.
... Unless you want to try to fix it? I am happy to supply more of that
kind of infor if you care.
Robby
On Wednesday, March 30, 2016, Tim Brown wrote:
> Robby,
>
>
Robby,
Maybe I’m being a bit thick, but that reply is a bit too cryptic for me
:-/
Should I be doing something?
[Can’t see how, since I’m just running racket]
Are the Racket devs being pestered to pass late-neg-projection where
they aren’t currently?
Or what?
Regards,
Tim
On 29/03/16 13:23,
It is well known but maybe not well liked. :)
Robby
On Tuesday, March 29, 2016, Tim Brown wrote:
> Folks,
>
> I have just upgraded some software to use Racket 6.4. My code sets
> log-max-level to debug, and then cranks up the level on the more
> chatty contributors.
>
> In 6.4, a new warning (o
Folks,
I have just upgraded some software to use Racket 6.4. My code sets
log-max-level to debug, and then cranks up the level on the more
chatty contributors.
In 6.4, a new warning (or collection of warnings) is thrown by the
racket/contract topic.
Is this intentional?
The warning is raised by
4 matches
Mail list logo
