Oh, I'm not sure. I don't maintain the machine that serves that
content myself. If it stays down, I can contact the maintainers, tho.
Robby
On Sat, Jul 18, 2015 at 6:21 PM, Alexander D. Knauth
wrote:
> And now it's up again!
>
> But it wasn't just me, because I think it was also down for my Trav
And now it's up again!
But it wasn't just me, because I think it was also down for my Travis CI builds
of afl.
On Jul 18, 2015, at 7:18 PM, Robby Findler wrote:
> Seems to be up for me. Also
> http://downforeveryoneorjustme.com/plt.eecs.northwestern.edu
>
> Robby
>
> On Sat, Jul 18, 2015 at
Seems to be up for me. Also
http://downforeveryoneorjustme.com/plt.eecs.northwestern.edu
Robby
On Sat, Jul 18, 2015 at 6:11 PM, Alexander D. Knauth
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this gro
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To
On Jul 18, 2015, at 5:31 PM, Matthew Flatt wrote:
> At Sat, 9 May 2015 06:59:53 -0600, Matthew Flatt wrote:
>> At Thu, 16 Apr 2015 17:39:50 -0400, "Alexander D. Knauth" wrote:
>>>
>>> On Apr 16, 2015, at 8:17 AM, Matthew Flatt wrote:
>>>
I don't think a "hygienic" reader extension works
I think this is the essentially same issue as in `afl` in the thread
where I just re-replied.
It looks like `curly-fn` wasn't introducing a mark the way that `afl`
did, and so it wasn't defending against a local `let` binding with the
old expander. For example,
#lang curly-fn racket
(let ([let
At Sat, 9 May 2015 06:59:53 -0600, Matthew Flatt wrote:
> At Thu, 16 Apr 2015 17:39:50 -0400, "Alexander D. Knauth" wrote:
> >
> > On Apr 16, 2015, at 8:17 AM, Matthew Flatt wrote:
> >
> > > I don't think a "hygienic" reader extension works in the old expander,
> > > either. The `lambda` produce
I’ve found an error that I believe is the fault of my curly-fn package under
the new macro-expander, but it’s a little bit odd, and I’m having trouble
figuring out exactly what the problem is. Specifically, the error doesn’t occur
within the curly-fn package itself, only a package that depends o
