David Anthoff

@c42f could we add a `parse!` version that accepts a `String`? It seems that `ParseStream` already supports constructors that accept that, so that seems a very simple solution here, as...

That is true, we can easily go back to the CSTParser situation by just reporting the first error. Having said that, it would be nice if the error recovery here...

https://github.com/dotnet/roslyn/issues/16151#issuecomment-269741300 is interesting. I would imagine that in the case I linked to, we detect that a closing `)` is missing, and then bubble up one level and continue parsing...

I started to surface JuliaSyntax.jl errors and warnings in the VS Code extension now (and also in a new GitHub lint action). And I'd really like to _not_ just show...

Take everything that follows with a grain of salt because I'm still trying to understand JuliaSyntax and might mix things up :) But here we go. If I understand what...

I can't replicate this right now. Are you removing these breakpoints while the debugger is paused, or just while the program is actually running?

If Juliaup is installed via the shell script (essentially Linux/Mac), then there are two config files, one is specifically for the config settings for the self-update of Juliaup itself. That...

I'm fairly positive that things will break if we move to a last-write-wins strategy. The config file is not just updated by explicit commands like `juliaup add` but also with...

> That said, I don't see a good reason to use a separate lock file in conjuction with posix advisory locks here. We should either be using pid files like...

Just to be clear, I don't want us to remove the locking. I think locking _with_ atomic file operations would be great. But that wouldn't fix #561. I describe what...