@samth I worked around the issue in the end using prop:procedure
and prop:struct-info
.
Does an unsafe-poller
need to do anything specific to cooperate with sync/enable-break
? Since its poll
argument is run in atomic mode, I would assume the answer is “no”, but I’m seemingly able to race a call to (sync/enable-break my-evt)
against a break and end up with both the break occurring and the event consumed. This only happens on CS, never on BC. Context <https://github.com/racket/unix-socket/pull/4/files#r544170166|here. >
That’s almost certainly a CS bug.
Should I file an issue? I’m running commit 627c45e8d4, if that’s relevant.
Yes, please
@gierczak.o has joined the channel
@nurrukia1 has joined the channel
the efficiency advantages of mutable strings could all be achieved with mutable string builders instead
I may need to look into making a string builder type, then.
open-output-string is a string builder, although it doesn’t always have the most convenient API
However, I’m skeptical that all efficiencies are possible just with string builders