I don't know whether or not it would satisfy your requirements, but it
may be worth a look to see if the documentation portion of 'raco
setup' comes close. You would want to run it in parallel to maximize
the memory use.
I believe that if you change some whitespace in the contract system
implement
Before noticing this email, I noticed that the build had failed on
Racket HEAD with a segfault. Builds for all other Racket versions were
OK.
I figured it was some temporary weirdness on HEAD, and without
thinking much, I restarted the build on Travis.
This time it succeeded fine, even on HEAD.
Those nondeterministic errors are in the Racket test suite, so probably
they wouldn't happen in the rackjure tests.
Sam
On Jul 11, 2014 8:10 PM, "Robby Findler"
wrote:
> No. But there are non-deterministic failures that travis sometimes
> finds, elsewhere in Racket. I didn't see the link to the
No. But there are non-deterministic failures that travis sometimes
finds, elsewhere in Racket. I didn't see the link to the travis
output. Do you have that handy?
Robby
On Fri, Jul 11, 2014 at 6:15 PM, Alexander D. Knauth
wrote:
> I was trying to make docs for ~>% and ~>_ in my fork of rackjure,
You should probably change this so that drdr runs the right tests.
Changing the module+ main to module+ test is probably the way to go.
Robby
On Fri, Jul 11, 2014 at 5:02 PM, Stephen Chang wrote:
> I merged. Thanks again!
>
>> the interesting thing is that running
> `./racket/bin/raco test pkgs
I was trying to make docs for ~>% and ~>_ in my fork of rackjure, and the
travis cl builds were passing,
but then I changed one character in the documentation to fix a typo and then
all of a sudden the build failed.
All I did was change one % to an _ within a @racketblock so this:
@racketblock[
(
I merged. Thanks again!
> the interesting thing is that running
`./racket/bin/raco test pkgs/lazy` seems to pass even when I add a
failing test case such as `(! (eq? 1 2)) => #t`.
That same test will fail as expected if I run it within drracket.
Thats because lazy currently doesn't use the "test
Greg,
You are right, managing the scrolling bars manually and
creating an in-place cell editor by demand seems
the only way under given circumstances.
I agree that other platforms have the same limitations
with GUI performance as Racket has. However, other platforms
may have a spreadsheet control
Doug,
Interesting suggestion, thanks!
A screen can easily contain ~ 50x30 cells, which is too many
if I want to have cells as text controls. So I think I will resort to
a big canvas instead of a table of cells. But I think I will use
the approach that you proposed for row/column controls (buttons
I just sent a pull request : https://github.com/plt/racket/pull/727
I added a few simple test cases, but the interesting thing is that running
`./racket/bin/raco test pkgs/lazy` seems to pass even when I add a failing
test case such as `(! (eq? 1 2)) => #t`.
That same test will fail as expected i
hello racket users, i'm looking for a specific type of racket programs
to test my garbage collector. particularly, programs that have large
working sets (GBs) and typically modify only a small portion of that
working set. please let me know if you have or know where i can find
such a program writte
On Fri, Jul 11, 2014 at 12:36 AM, Robby Findler
wrote:
> Oh, I'm not sure of the best way, but way that should work is if you
> port that one by hand. Just remove it from the bibtex file in question
> and write out the corresponding call to make-bib. (I hope you'll find
> that Matthew's API is a l
Thanks for the explanation!
Laurent
On Thu, Jul 10, 2014 at 12:50 PM, Matthew Flatt wrote:
> I think the ordering of submodules is unavoidable, but the
> documentation should make more clear that the order of `module*`
> declarations matters.
>
> Meanwhile, the documentation for `module+` need
Greetings.
On Thu, Jul 10, 2014 at 4:01 PM, Joe Gibbs Politz wrote:
> I was getting some odd behavior on authors whose names ended in "and"
> when compiling a bibliography, and dug into the source a bit. A
> little armchair debugging: should this line
>
> https://github.com/plt/racket/blob/88d
14 matches
Mail list logo
