> On May 14, 2015, at 4:08 PM, Matthew Flatt wrote:
>
> Here are the results of a package build using the v6.2 release
> candidate:
>
> http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/
>
> Compare to v6.1.1:
>
> http://pkg-build.racket-lang.org/
I believe I’ve fix
This is OT wrt deps and doc, but:
I don't understand this reported test failure for rackjure, on both
versions of Racket:
test.rkt: raco test: non-empty stderr:
#"\nFAILURE\nname: check-exn\nlocation:
(#
68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eva
What happened was a new _documented_ export was added to `racket/match`:
`match-define-values`. But yes, creating some dedicated test modules is a
good idea so that this doesn't happen every release.
Sam
On Fri, May 15, 2015 at 3:28 AM Jack Firth wrote:
> On Thursday, May 14, 2015 at 5:36:23 PM
At Fri, 15 May 2015 11:09:25 -0400, Philip Blair wrote:
> One question I have is whether or
> not the scopes feature is something which I can more or less count on being
> available in future versions of Racket
That's not yet clear.
Although most existing code would be unaffected by the change to
Sorry for the delay (I was moving earlier this week).
Thank you for taking a crack at the task. One question I have is whether or
not the scopes feature is something which I can more or less count on being
available in future versions of Racket (I understand that it's from a
snapshot and might the
On Thursday, May 14, 2015 at 5:36:23 PM UTC-7, Matthew Flatt wrote:
> Here are the results of a package build using the v6.2 release
> candidate:
>
> http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/
>
> Compare to v6.1.1:
>
> http://pkg-build.racket-lang.org/
>
>
6 matches
Mail list logo
