Yes, fix (for the internal error) coming soon.
Sam
On Tue, Nov 18, 2014 at 5:24 PM, Alexander D. Knauth
wrote:
> In terms of bugs, it’s probably related to this problem with call-with-values
> and poly-dots:
> #lang typed/racket
> (: f : (All (a ...) [(-> (values Any ... a)) -> Void]))
> (defin
In terms of bugs, it’s probably related to this problem with call-with-values
and poly-dots:
#lang typed/racket
(: f : (All (a ...) [(-> (values Any ... a)) -> Void]))
(define (f g)
(call-with-values g void))
;=>
. . ../../Applications/Racket
v6.1.1/share/pkgs/typed-racket-lib/typed-racket/type
I am sending you the status line from
DrRacket, version 6.1.1.5--2014-11-18(c4684c12/d) [3m].
On Nov 18, 2014, at 12:10 PM, Sam Tobin-Hochstadt wrote:
> With that program, I get this error message:
>
>unsaved editor:7:48: Type Checker: parse error in type; type
> variable must be u
With that program, I get this error message:
unsaved editor:7:48: Type Checker: parse error in type; type
variable must be used with ... variable: Y in: Y
Which you also got. What changed it from the parse error to the
"unbound identifier" error?
Sam
On Tue, Nov 18, 2014 at 12:05 PM, Matthi
What I sent is the exact program that produced the attached error in today's
drracket [updated around 10am].
On Nov 18, 2014, at 11:58 AM, Sam Tobin-Hochstadt wrote:
> No, I ran it, it barfed, and then I figured out what went wrong. Then
> I sent you an email with a fix. Unfortunately, tha
No, I ran it, it barfed, and then I figured out what went wrong. Then
I sent you an email with a fix. Unfortunately, that fix isn't enough
to make the program type check. Partly, there's an internal error, but
that's a missing case that will take work to support properly.
We can do better with the
Attached is the screen shot of the error report.
On Nov 18, 2014, at 11:54 AM, Matthias Felleisen wrote:
>
> On Nov 18, 2014, at 11:34 AM, Sam Tobin-Hochstadt
> wrote:
>
>> On Tue, Nov 18, 2014 at 10:45 AM, Matthias Felleisen
>> wrote:
>>>
>>> It's quite possible that this is Eli's b
On Nov 18, 2014, at 11:34 AM, Sam Tobin-Hochstadt wrote:
> On Tue, Nov 18, 2014 at 10:45 AM, Matthias Felleisen
> wrote:
>>
>> It's quite possible that this is Eli's bug again, but boy this causes
>> headaches:
>>
>>> Type Checker: parse error in type;
>>> type variable must be used with ...
On Tue, Nov 18, 2014 at 10:45 AM, Matthias Felleisen
wrote:
>
> It's quite possible that this is Eli's bug again, but boy this causes
> headaches:
>
>> Type Checker: parse error in type;
>> type variable must be used with ...
>> variable: Y in: Y
>
> And it points precisely to where Y is follo
It's quite possible that this is Eli's bug again, but boy this causes
headaches:
> Type Checker: parse error in type;
> type variable must be used with ...
> variable: Y in: Y
And it points precisely to where Y is followed by ...
#lang typed/racket
(module+ test (require rackun
10 matches
Mail list logo