Re: [racket-users] Errors in (Dr)Racket

I understand entirely that this was not the sort of case you seemed to have in mind, but I'll follow up because I worry that, in the process of making a minimal example, I may have obscured the actual problem. "The fix can be easily located in [my] code" in the sense that it's clear that the error

Re: [racket-users] Errors in (Dr)Racket

> On Jan 2, 2017, at 7:25 AM, Philip McGrath wrote: > > > So why have I not complained about this? > > First, most generally, because the bug is clearly my fault. Hi Philip, thanks for this example. What Robby and I had in mind are calls to errors inside a

Re: [racket-users] Errors in (Dr)Racket

Stephen's mention of web server code reminded of me one of the very few situations when I've struggled with Racket error messages, so I'll both share an example and explain why I haven't complained about it before. Here's a buggy program: > #lang web-server > (require web-server/servlet-env >

Re: [racket-users] Errors in (Dr)Racket

I mostly agree with Matthias, but wanted to add two things: 1) I've certainly experienced, many times, (both as the producer and consumer (and sometimes simultaneously)) contracts that were added because of runtime errors. But I do agree it is not as common as we had hoped it would be. And

Re: [racket-users] Errors in (Dr)Racket

> On Jan 1, 2017, at 1:17 PM, Stephen De Gabrielle > wrote: > > Hi All, > > I occasionally write code with errors* that cause the DrRacket error message > to link to an internal Racket file, rather than my own incorrect code. > > The last time I did this it was

[racket-users] Errors in (Dr)Racket

Hi All, I occasionally write code with errors* that cause the DrRacket error message to link to an internal Racket file, rather than my own incorrect code. The last time I did this it was doing web server code, but I've also managed it with GUI code.(and playing with DrRacket Plugins) I've not