Thank you guys. I'll start to dig into it after a paper deadline.
Sam Tobin-Hochstadt 于2019年4月19日周五 上午7:29写道：
> On 1: the best thing to do is figure out (probably with logging) which
> call to MPFR and what arguments produce the assertion.
> 2: I don't think there's any intended
> On Apr 21, 2019, at 6:48 AM, zeRusski wrote:
>
> I just had an epiphany, or rather a very painful revelation, that if your
> macro does not report errors in terms of user code, say, when inputs are
> wrong, you ought to be ostracized by the community if not banished from any
> social
Hello everyone,
I observed some exceptions like `SIGSEGV MAPERR si_code 1 fault on addr
0x7f6f4e30fff0` when running a Racket program. Any ideas why this happens?
Thanks,
Shaobo
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe
On 18/04/2019 10:25, Alexander Shopov wrote:
> And a bit more popularity - there will be links from
> Linux Weekly News: Announcements -> Newsletters -> Developement to the
> news letter:
>
Hi Alex,
Many thanks for this. It looks great.
--
Paulo Matos
--
You received this message because
Match treats `empty` as an identifier to bind, not as a pattern for the empty
list. This means that the first case will always be matched. You can use
`(list)` or `'()` to match an empty list.
Also, in the last catch-all case, you pass the function `rest` which returns
the tail of a list to
Try
[rest (filter-odds rest]
as the last clause.
søn. 21. apr. 2019 kl. 22.19 skrev Tim Meehan :
> Forgive this naive question, I am having some trouble understanding some
> matching forms. If I wanted to filter out odd numbers like this:
>
> (filter odd? '(1 2 3 4 5)) => '(1 3 5)
>
> but
Forgive this naive question, I am having some trouble understanding some
matching forms. If I wanted to filter out odd numbers like this:
(filter odd? '(1 2 3 4 5)) => '(1 3 5)
but I wanted to do this with a match:
(define (filter-odds v)
(match v
[empty empty]
[(cons (? odd? first)
ICFP 2018 should be available to all (and other years too). It was paid for
and I can get the PDF.
Could you send me more info?
Robby
On Sun, Apr 21, 2019 at 12:53 PM Greg Hendershott
wrote:
> On Sat, Apr 20, 2019 at 12:02 PM Norman Gray
> wrote:
> > On 20 Apr 2019, at 1:11, 'John Clements'
On Sat, Apr 20, 2019 at 12:02 PM Norman Gray wrote:
> On 20 Apr 2019, at 1:11, 'John Clements' via Racket Users wrote:
>
> > There’s a paper at the most recent ICFP from Simon Peyton Jones (et
> > al., I’m guessing) on make languages, IIRC.
>
> Very interesting -- thanks! The paper is Andrey
One quick thought: I wasn't sure what to expect after reading the current title.
How about changing it to say more about the specific exploit?
"A terrible hack to move state across Racket phases"
"How to smuggle state across phase boundaries"
At least, it would have helped me if "separate
I just had an epiphany, or rather a very painful revelation, that if your
macro does not report errors in terms of user code, say, when inputs are
wrong, you ought to be ostracized by the community if not banished from any
social interactions altogether. You don't deserve the good life.
Hello all,
I just published a blog post on defeating Racket’s separate compilation
guarantee. While I don’t imagine such a thing is actually a good idea, I think
the path to getting there is interesting anyway, and it touches lots of
different parts of the Racket system. For those who are
On Saturday, 20 April 2019 23:55:50 UTC+1, Stephen Chang wrote:
>
> fwiw, I think here is a working version along the lines of your
> original attempt.
>
I see what you did there. This is both icky (as requested) and cute :0
Thanks, it's actually illuminating
--
You received this message
Matthias, thank you very much for taking the time to carefully read the
whole thing
and for your thoughtful suggestions. Most, if not all of them, put on the
foreground my own doubts and misgivings.
On Saturday, April 20, 2019 at 8:19:31 PM UTC+2, Matthias Felleisen wrote:
>
>
>
> > On Apr 18,
14 matches
Mail list logo
