Re: [racket-users] Towards an Incremental Racket Parser for better IDE experience?

A few thoughts on these topics, which I've been thinking about for a while. First, let's distinguish two things. One is an _incremental_ system, such as a parser, which is one which does less work in response to a small change than it would need to do from scratch. The other is a system with

Re: [racket-users] Towards an Incremental Racket Parser for better IDE experience?

Oh, and I should have pointed out that, at least for the read level, DrRacket already is incremental and can recover from errors. This helps only with the syntax coloring, however. Robby On Wed, Dec 2, 2020 at 9:10 AM Sorawee Porncharoenwase < sorawee.pw...@gmail.com> wrote: > IIUC, many tools

Re: [racket-users] Towards an Incremental Racket Parser for better IDE experience?

IIUC, many tools (Racket Mode , drcomplete ) do exactly what Robby said: cache the most recent successfully expanded code. On Wed, Dec 2, 2020 at 7:08 AM Robby Findler wrote: > I'm not sure this approach is going to work for

Re: [racket-users] Towards an Incremental Racket Parser for better IDE experience?

I'm not sure this approach is going to work for Racket. Being able to run `read` when the input is malformed is going to only get you so far, as the macro expansion seems unlikely to work and this is a point of extension for programers using Racket. Maybe a better approach would be to help

[racket-users] Towards an Incremental Racket Parser for better IDE experience?

Hi! The Racket Reader and the Racket Expander always return "Error : blabla" when you send it a bad Racket source code. As a consequence, when there is a source code error, DrRacket and the Racket LSP cannot provide IDE functionalities like "find references", "info on hover", "find