I wonder whether one could implement a translator refactoring
that simply inserts type annotation placeholders where needed.
It would probably generate a new buffer with the code and if
we add some inferencing tool that suggests types it is even
better
— Matthias
> On Mar 29, 2017, at 2:
> On Mar 29, 2017, at 3:27 PM, Christopher Munroe wrote:
>
> Are these only meant to be fired by the machine? I keep trying to send
> mouse-event% objects and it is not moving my mouse. What is the point of
> set-x if it doesn't actually set the x-coordinate of the mouse?
>
> Link to the docu
Are these only meant to be fired by the machine? I keep trying to send
mouse-event% objects and it is not moving my mouse. What is the point of set-x
if it doesn't actually set the x-coordinate of the mouse?
Link to the document I am referencing:
https://docs.racket-lang.org/gui/mouse-event_.ht
This example and variants exposed multiple problems with the
implementation of chaperones, and I've pushed repairs.
At Wed, 29 Mar 2017 09:12:25 -0600, Matthew Flatt wrote:
> It's also not really contracts, but chaperones:
>
> #lang racket/base
>
> (define kwstruct-add1
>(let ()
> (st
DrRacket is happy to accept other directives along the lines of the
ones it gets for tooltips, of course! :)
Robby
On Wed, Mar 29, 2017 at 1:40 PM, Asumu Takikawa wrote:
> On 2017-03-29 08:54:16 -0700, Raoul Duke wrote:
>>Does/could the IDE hilight places based on this:
>>
>> [1]http://
On 2017-03-29 08:54:16 -0700, Raoul Duke wrote:
>Does/could the IDE hilight places based on this:
>
> [1]http://docs.racket-lang.org/ts-guide/more.html#%28part._when-annotations~3f%29
That's an interesting idea. Currently the only interaction that TR has with the
IDE is
making tooltips th
Does/could the IDE hilight places based on this:
http://docs.racket-lang.org/ts-guide/more.html#%28part._when-annotations~3f%29
I'd like to not have to manually mentally worry about the rules. :-}
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group
It's also not really contracts, but chaperones:
#lang racket/base
(define kwstruct-add1
(let ()
(struct the-struct ()
#:property prop:procedure
(make-keyword-procedure (λ (kws kw-values _ i) "broken")))
(the-struct)))
((chaperone-procedure kwstruct-add1 (make-keywor
I think the problem is actually in the implementation of
`chaperone-procedure` for keywords. This program has the same
behavior:
#lang racket
(require (prefix-in k: '#%kernel))
(define kwstruct-add1
(let ()
(struct the-struct ()
#:property prop:procedure
(make-keyword-procedure (
This is actually a problem in racket/contract with applicable structs
where prop:procedure is a keyword procedure. This file shows the
development --- http://pasterack.org/pastes/361 --- and the simple
thing that breaks is:
#lang racket
(define kwstruct-add1
(let ()
(struct the-struct ()
10 matches
Mail list logo