Yuck.
On Apr 15, 2014, at 9:20 PM, as...@racket-lang.org wrote:
asumu has updated `master' from aa43797b63 to 9aaaf98b32.
http://git.racket-lang.org/plt/aa43797b63..9aaaf98b32
=[ One Commit ]=
Directory summary:
97.6%
On Apr 15, 2014, at 9:29 PM, Asumu Takikawa as...@ccs.neu.edu wrote:
On 2014-04-15 18:13:31 -0400, claire alvis wrote:
The push below includes changes to letrec expressions, internal
definitions, units, classes, and certain ill-formed shared expressions so
that they no longer leak the
Ah, too bad:
pkgs/racket-pkgs/racket-test/tests/racket/optimize.rktl
~~~
--- OLD/pkgs/racket-pkgs/racket-test/tests/racket/optimize.rktl
+++ NEW/pkgs/racket-pkgs/racket-test/tests/racket/optimize.rktl
@@ -3416,5 +3416,16 @@
At Wed, 16 Apr 2014 09:02:44 -0400, Matthias Felleisen wrote:
On Apr 15, 2014, at 9:29 PM, Asumu Takikawa as...@ccs.neu.edu wrote:
On 2014-04-15 18:13:31 -0400, claire alvis wrote:
The push below includes changes to letrec expressions, internal
definitions, units, classes, and certain
I hope this isn’t a self-service question too…
Who manages the public keys accepted by git.racket-lang.org, now that it’s not
Eli’s job? I’m attaching my new public key.
Ooh, I guess I should also ask; has that machine been patched? Looks like it
has, but I just used some random online tool.
(moved to dev)
On Linux, the attached program shows terrible responsiveness when
dragging points around on the graph. Can anyone else on Linux reproduce
this behavior?
The patch below dramatically improves the responsiveness by forcing the
eventspace to process medium-level events (mouse
You're right that it's about event ordering and not refresh coalescing.
Since mouse events are handled after refreshes, you won't get the next
refresh request until an earlier one is handled, after which the next
mouse event can trigger another refresh request. I think the difference
between
Can we make sure that some warning appears on the entire page so that nobody
loses track of this? A linked margin note every 10 lines would be fine.
On Apr 16, 2014, at 2:59 PM, as...@racket-lang.org wrote:
asumu has updated `master' from d212fc7eba to d6a3d27e54.
That seems quite drastic. For the `unstable` collection, it's worked
fine just having the warning at the top of each page.
Sam
On Wed, Apr 16, 2014 at 6:07 PM, Matthias Felleisen
matth...@ccs.neu.edu wrote:
Can we make sure that some warning appears on the entire page so that nobody
loses
Thanks for the great (and quick!) response. It's good to know that the
ordering is intentional, and to have some nice ways to work around it if
needed.
The reason I thought that refreshes were lower priority was because of
the scrollbar behavior in the program below. On Unix/X, dragging the
This one's different, given our discussion while you were flying home.
On Apr 16, 2014, at 6:07 PM, Sam Tobin-Hochstadt sa...@cs.indiana.edu wrote:
That seems quite drastic. For the `unstable` collection, it's worked
fine just having the warning at the top of each page.
Sam
On Wed,
No, I think it's very much the same -- like unstable, changes to the
type system for classes may cause programs that worked (accidentally)
in 6.0.1 to stop working later. The situtation with `unstable` is in
fact more unstable, since the interface may change or disappear
entirely.
Sam
On Wed,
TOOR is not in /unstable/. I am with Robby here. Make sure people know.
On Apr 16, 2014, at 6:15 PM, Sam Tobin-Hochstadt sa...@cs.indiana.edu wrote:
No, I think it's very much the same -- like unstable, changes to the
type system for classes may cause programs that worked (accidentally)
in
On 2014-04-15 21:19:16 -0600, Neil Toronto wrote:
Does TR not having to worry about #undefined mean that the following
program will typecheck?
#lang typed/racket
(define-type (Lazy-Listof A) (Promise (Pair A (Lazy-Listof A
(let ()
(define: lazy-zeros : (Lazy-Listof Zero)
14 matches
Mail list logo
