[racket-users] Do you have Racket programs whose performance you care about?

2020-02-28 Thread Lukas Lazarek
PLT @ Northwestern is seeking out programs to help us understand the performance of Racket "in the wild". If you have any Racket applications that you use and care about how it performs, please let us know about them in the following survey: https://forms.gle/b2eKMZdvXjpRHKL38 Thank you! PLT

Re: [racket-users] a little bug

2020-02-28 Thread Hendrik Boom
On Fri, Feb 28, 2020 at 07:11:02AM -0600, Robby Findler wrote: > Oh, sorry-- I misunderstood. > > In v7.5, there will be, in some cases, a source location after you > dismiss that dialog. In the pre-release builds, that's been improved > somewhat and source location information is more reliably

Re: [racket-users] a little bug

2020-02-28 Thread Robby Findler
Oh, sorry-- I misunderstood. In v7.5, there will be, in some cases, a source location after you dismiss that dialog. In the pre-release builds, that's been improved somewhat and source location information is more reliably available. That said, there are limitations and it isn't always available.

Re: [racket-users] a little bug

2020-02-28 Thread Hendrik Boom
On Fri, Feb 28, 2020 at 06:02:31AM -0600, Robby Findler wrote: > I agree that would be great. In the meantime, the Run button does a better > job with error reporting in various ways, including this one so hopefully > you can try that? That's what I was using. There was a popup message that

Re: [racket-users] a little bug

2020-02-28 Thread Robby Findler
I agree that would be great. In the meantime, the Run button does a better job with error reporting in various ways, including this one so hopefully you can try that? Robby On Fri, Feb 28, 2020 at 5:45 AM Hendrik Boom wrote: > > When Racket detects the out-of-memory condition during

Re: [racket-users] a little bug

2020-02-28 Thread Hendrik Boom
When Racket detects the out-of-memory condition during "background processing", it would be useful i the out-of-memory message were to point out which particular piece of source text it was having trouble with. Just the line number where the expression started that the REPL was having