Here is one example.
(make-discrete-histogram
(case- (-r ((n1 integer?)
(n2 (and/c integer?
(=/c n1)))
(dynamic? boolean?))
discrete-histogram?)
(-r ((n1 integer?)
(n2 (and/c integer?
On Mon, Oct 25, 2010 at 10:06 AM, Doug Williams
m.douglas.willi...@gmail.com wrote:
(case- (-r ((r random-source?)
(a real?)
(b (/c a)))
real?)
(-r ((a real?)
(b (/c a)))
real?)))
I'm not sure that
Thanks, that's a great example. The idea (at least from the contract's
point of view) is that there are two different functions with one name
that have two different arities, I think.
So maybe the right way to bring back case- is that contracts that
match functions should come with some way to
At Fri, 22 Oct 2010 21:31:43 -0600, Doug Williams wrote:
Matthew, would it make more sense to have unsafe-vector-ref (and related
functions) be the more general function and unsafe-vector*-ref be the one
that doesn't work on chaperoned vectors? That is just swap the definitions.
That way user
Checklist items for the v5.0.2 release
(using the v5.0.1.900 release candidate build)
Search for your name to find relevant items, reply when you finish an
item (please indicate which item/s is/are done). Also, if you have any
commits that should have been picked, make sure that the changes
On Mon, Oct 25, 2010 at 11:28 AM, Doug Williams
m.douglas.willi...@gmail.com wrote:
I had always assumed that case-lambda just checked alternatives in order
until one matched - like a cond. But, that was just an assumption on my part
and subject to being absolutely wrong. [But, if it is correct
I think CM already does this, no (that's how drracket builds zo files
for you, for example)? So it needs to be packaged up a little bit,
perhaps, for some settings in your .racket file?
You might look at how the PLTDRCM environment variable is implemented,
if the docs aren't helpful enough.
On 10/25/2010 02:54 PM, Jon Rafkind wrote:
I would like on-demand compilation of the collects tree. It seems there
are two reasons why it doesn't exist right now
1. building the documentation requires the collects tree to be touched,
so its worthwhile to just compile everything in there
2. users
On Mon, Oct 25, 2010 at 4:54 PM, Jon Rafkind rafk...@cs.utah.edu wrote:
My motivation is to quickly test changes to core libraries (like
collects/racket) after doing a 'git pull --rebase'.
Given that this is your motivation, why not just use:
'raco setup -D'
which skips the documentation
On Mon, Oct 25, 2010 at 5:15 PM, Jon Rafkind rafk...@cs.utah.edu wrote:
On 10/25/2010 03:06 PM, Sam Tobin-Hochstadt wrote:
On Mon, Oct 25, 2010 at 4:54 PM, Jon Rafkind rafk...@cs.utah.edu wrote:
My motivation is to quickly test changes to core libraries (like
collects/racket) after doing a
Four hours ago, Matthew Flatt wrote:
I've pushed a change (intended to be merged to 5.0.2) that
swaps
`unsafe-vector-ref'- `unsafe-vector*-ref'
`unsafe-vector-set!' - `unsafe-vector*-set'
`unsafe-vector-length' - `unsafe-vector*-length'
`unsafe-unbox' - `unsafe-unbox*'
Oh, yes. Just run make install and then raco setup -D racket.
Write it down on a postit and stick it on your screen. :) Or make a
little script that does the whole git pull thing and onwards.
Robby
On Mon, Oct 25, 2010 at 4:22 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote:
On Mon, Oct 25,
If I run 'racket -f quiet.rktl' in collects/tests/racket a bunch of
collects will be pulled in (mzlib, scheme, racket, etc.). So I would
need to do 'raco setup -D racket mzlib scheme', not to mention first
figure out what collections are pulled in to begin with.
On 10/25/2010 03:57 PM, Robby
So what's wrong with just `raco setup -D'?
An hour ago, Jon Rafkind wrote:
If I run 'racket -f quiet.rktl' in collects/tests/racket a bunch of
collects will be pulled in (mzlib, scheme, racket, etc.). So I would
need to do 'raco setup -D racket mzlib scheme', not to mention first
figure out
9 hours ago, Ryan Culpepper wrote:
[...]
-- Release candidates are at
-- http://pre.racket-lang.org/release/installers
There is now a build there that includes Matthew's change to the
unsafe bindings. (As I said earlier -- it would be good to re-run
tests that are contract-heavy, even if
15 matches
Mail list logo
