Re: [racket-users] Webserver HTTP 2

I am very confident that it will eventually support it. ;) However, I have no current plans to go implement it. It's on my long list of things to eventually get to, but is not blocking me on any other things. If someone else were passionate about it, I'd be happy to help them get started, etc.

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

You have gotten plenty of good answers so let me focus on some of the high-level points and some details that people didn’t respond to: > On May 2, 2017, at 6:01 PM, Daniel Prager wrote: > > More concise and clear expression of contracts > • The implies

[racket-users] break-thread + thread-wait can't be handled

Hello, I'm having trouble catching "terminate break" exceptions when combining break-thread with thread-wait. MWE 1: (with-handlers ([exn:break:terminate? writeln]) (let ([t (thread (lambda () (thread-wait (current-thread]) (break-thread t 'terminate) (thread-wait t)))

Re: [racket-users] break-thread + thread-wait can't be handled

On 5/3/17 10:41 PM, Eric Griffis wrote: Hello, I'm having trouble catching "terminate break" exceptions when combining break-thread with thread-wait. MWE 1: (with-handlers ([exn:break:terminate? writeln]) (let ([t (thread (lambda () (thread-wait (current-thread])

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

Hi Philip Thank-you for sharing your version: each example and variation is helping me understand the machinery better. I agree that clarity in error reporting is also vital, and it's been made clear to me that it is feasible to hook into the contract system and take advantage of its facilities,

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

Hi Matthias (and everyone) Matthias wrote: > As Tony Hoare said, what do you think of a boater who practices on land with his swim vest on and then goes to sea and takes the swim vest off? I think the only way to reply to these sorts of arguments is to wrestle back the framing! Do you bet on

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

> On May 3, 2017, at 10:01 PM, Daniel Prager wrote: > > Do you bet on the Formula I driver whose team includes the most safety > features? ;-) Yes. He’s more like to survive and get across the goal line :)) > From a technical perspective I'm happy to not mention

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

Thanks Ben The left-pad example is most helpful. Perhaps it could be included in the docs, given that usefully illustrates features of ->i for which no example is given. I may well have a shot at re-implementing it once I have sufficient machinery set up to support multiple and optional

[racket-users] Webserver HTTP 2

Hello, Does anyone know if the Racket webserver will support http2 at any stage? Kind regards, Sean -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [racket-users] How to improve compile times?

Am 28.04.2017 um 08:07 schrieb Alex Harsanyi: > > In the end, the start up time does not bother me too much, as it is a GUI > application and I spend a lot of time using it after starting it up, so the 7 > second wait is acceptable. I have other, more interesting, application > features to

Re: [racket-users] Apropos contracts: simple predicates and switching on and off

Using Ben's left-pad example as a model I get the following re-write of the real-sqrt contract (([x real?]) #:pre/name (x) "non-negative argument expected" (>= x 0) . ->i . [result (x) real?] #:post/name (x result) "the sqrt of zero is zero" (implies (= x 0) (= result