Thanks for that version. I will update it today.
On Tuesday, 4 August 2020 at 12:06:12 UTC+2 laurent...@gmail.com wrote:
> Thanks Paulo, very interesting and useful as usual!
>
> This version of the featured paper "Hygienic macro expansion" is a little
> more readable:
> https://prl.ccs.neu.edu/
Awesome, I didn't know about thread groups. I'll check into that as an
option. I appreciate all your help!
On Tuesday, August 4, 2020 at 2:14:17 PM UTC-6, Matthew Flatt wrote:
>
> At Tue, 4 Aug 2020 14:01:20 -0600, Robert D Kocisko wrote:
> > My only concern with this is whether that single th
At Tue, 4 Aug 2020 14:01:20 -0600, Robert D Kocisko wrote:
> My only concern with this is whether that single thread might get mildly
> starved compared to other racket threads given that it technically
> represents hundreds of 'green threads' inside itself all implemented in C
> whereas every othe
Genius! I had forgotten that the FD returned from epoll_create can itself
be polled to indicate when any of the currently registered fds are ready to
be processed. That simplifies everything for sure.
Given all the above I'm planning to pass the epoll FD to unsafe-fd->evt and
then sync on it in a
You're right: I had momentarily confused epoll with poll. You can just
use the single file descriptor for an epoll object with things like
`unsafe-file-descriptor->semaphore`, or you can use `unsafe-poller`.
I'll note that `unsafe-file-descriptor->semaphore` scales to a large
number of file descri
Thanks Matthew! That was my thought but given the number of fds in play
and the frequency of adding and removing interest in them (they are added
dynamically as needed) it seems like that option would be rather
inefficient.
Is there by chance any 'magic back door' which would allow me to register
The prop:struct-field-info doc could also be accessed at
https://plt.eecs.northwestern.edu/snapshots/current/doc/reference/structinfo.html?q=prop%3Astruct-field-info#%28def._%28%28lib._racket%2Fstruct-info..rkt%29._prop~3astruct-field-info%29%29
.
On Tue, Aug 4, 2020 at 7:33 AM 'John Clements' via
Yes, there is documentation for this feature! Here are two ways to get it:
1) On a machine with 7.8 installed, run `raco docs prop:struct-field-info` at
the command line, or (equivalently) highlight the word in drracket and hit F1.
Both of these open a web browser window pointed at your local do
I'm very interested in the prop:struct-field-info property. Is there any
documentation on it? I notice docs.racket-lang.org still says 7.7 up at the
top.
Thanks to everyone for this release!
On Monday, August 3, 2020 at 12:19:57 PM UTC-5 johnbclements wrote:
> This release announcement mistake
Fusing event loops is always tricky, but if you have the option of
exposing individual file descriptors to Racket, then `ffi/unsafe/port`
is probably the way to go. You can turn a file descriptor into an event
using `unsafe-file-descriptor->semaphore` or `unsafe-fd->evt`, and then
you can block on
On Mon, Aug 3, 2020, 7:27 PM Hendrik Boom wrote:
> On Mon, Aug 03, 2020 at 02:01:16PM -0400, Philip McGrath wrote:
> > Is this what you're looking for?
> https://pkgs.racket-lang.org/package/sgl
> >
> > -Philip
>
> Yes, looks like it. Is it messing from the index for some good reason?
>
By defa
Thanks Paulo, very interesting and useful as usual!
This version of the featured paper "Hygienic macro expansion" is a little
more readable:
https://prl.ccs.neu.edu/img/kffd-tr-1986.pdf
Or would Matthias be able to provide a freshly compiled version maybe? :)
(I would be truly impressed if the te
Racket News Issue 36 is here!
https://racket-news.com/2020/08/racket-news-issue-36.html
Grab yourself your favourite cup and pour in some good ol'coffee.
Enjoy!
Paulo Matos
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from th
13 matches
Mail list logo
