Re: [racket-users] Typed Racket & Higher Kinded Types

And how would components in #lang typed/racket interact with components in #lang kinded/racket interact? > On Jan 18, 2017, at 8:16 PM, Anthony Carrico wrote: > > On 01/17/2017 05:31 AM, Sam Tobin-Hochstadt wrote: >> The major obstacle is that the current kind system

Re: [racket-users] Typed Racket & Higher Kinded Types

On 01/17/2017 05:31 AM, Sam Tobin-Hochstadt wrote: > The major obstacle is that the current kind system design is not easy to > reconcile with higher kinds. This is mostly because the current system > is poorly designed, but we need to avoid breaking existing programs. Why is this an issue? #lang

[racket-users] Dynamic-require a compile-time identifier?

Is there a way to dynamic-require an identifier provided at phase 1? #file x.rkt #lang racket (provide (for-syntax x)) ; x is provided at phase 1 (define-for-syntax x 3) #file use.rkt #lang racket (dynamic-require-from-phase-1 "x.rkt" 'x) ;=> 3 I could do it by defining another module that did

[racket-users] Serializing macro transformer procedures

I'm trying to use serial-lambda in macro transformer procedures so that I can serialize them and bring them down to run-time. However, serial-lambda isn't working within a define-syntax. It says: syntax-local-lift-provide: not expanding in a module run-time body This seems to be a lie; it

Re: [racket-users] Bugs in the Racket Bytecode Versifier (as of 6.7)

The bug is a mismatch between the optimizer and validator, where the optimizer can see that `string-append` is applied to a string and will definitely succeed, while the validator can't infer that behavior. The fact by itself isn't the problem, but it allows a further inference in the optimizer

[racket-users] Bugs in the Racket Bytecode Versifier (as of 6.7)

Hey all, I noticed that the following program fails to run, but only after its been compiled (on 6.7, 6.6 and earlier don't seem to have this issue): https://gist.github.com/LeifAndersen/dfad9a8f55ef671e4f3aa41b321ef7bf #lang racket/base ;; ill-formed.rkt (define ill (let ((base

[racket-users] Re: can't open/start DrRacket v6.8.0.2 on macOS Sierra 10.12.2

Thanks Alex, Vincent and Robby [and Matthew]! I'll remember all your tricks. What worked this time was the Matthew-trick Robby referenced about moving the .app to the enclosing folder and then putting it back in the correct folder. But it's good to know there are other ways. Geoff -- You

Re: [racket-users] DrRacket Background Expansion Memory Usage

The program I've been working on is https://github.com/lehitoskin/ivy - it has a few library dependencies, but those should be easy to get. On Wednesday, January 18, 2017 at 4:04:01 AM UTC-8, Robby Findler wrote: > It sounds like there might be a leak somewhere. Is the program you were >

Re: [racket-users] can't open/start DrRacket v6.8.0.2 on macOS Sierra 10.12.2

> the meantime, 6.8 pre-release builds are available from > pre-release.racket-lang.org (and should also be signed). > > Signing nightly builds is on the to-do list. > > Vincent > > > > On Wed, 18 Jan 2017 09:45:03 -0600, > Geoffrey Knauth wrote: >> >> I d

Re: [racket-users] can't open/start DrRacket v6.8.0.2 on macOS Sierra 10.12.2

> On Jan 18, 2017, at 4:45 PM, Geoffrey Knauth <ge...@knauth.org> wrote: > > I downloaded the 20170118 nightly 64bit Mac version of DrRacket v6.8.0.2, and > I just can't open the application at all. It shuts down immediately. I've > had this with other applications on

[racket-users] can't open/start DrRacket v6.8.0.2 on macOS Sierra 10.12.2

I downloaded the 20170118 nightly 64bit Mac version of DrRacket v6.8.0.2, and I just can't open the application at all. It shuts down immediately. I've had this with other applications on Sierra, and rebooting the Mac fixed the problem, but this time I can't get the newest snapshot to start

Re: [racket-users] DrRacket Background Expansion Memory Usage

It sounds like there might be a leak somewhere. Is the program you were editing easy to share? Robby On Wed, Jan 18, 2017 at 1:56 AM Lehi Toskin wrote: > In DrRacket I had background expansion on for the longest time until I > started to notice that whenever I would work