Claire Foster

Just supporting julia syntax for round-tripping and the current syntax for pretty printing would be fine by me. It seems straightforward and explicit. --- Continuing some conversation from #214 >...

Thanks for the pointers. There's a key part which I don't understand in this suggestion: how do we have `001-rollback.sql` tracked by the system, but not applied to the production...

> I don’t like the idea of inline comments because our migration/current files should be runnable with psql without needing custom parsing Yes that makes sense. The thing I don't...

> we could even expose it in an envvar and move rather than delete True! I think this is the right idea.

Yikes, https://github.com/JuliaLang/julia/issues/4630 has some pretty strong opinions there. To be honest, my main gripe with the current `juliaup` default installation location is that it's creating a special `.juliaup` directory just...

> So in my ideal world we would somehow detect whether there is a user profile specific folder that is already on the PATH (like ~/.local/bin) I did some investigation...

The docs say > If macros would get informed about whether they are defined within another function The difficulty I see with this is that macros are expanded *prior* to...

Yes indeed, I noticed you'd just added those cases recently in Base :sweat_smile: If you look in the JuliaSyntax tests you'll see there's a plan in motion to parse all...

Additionally, there's a list of other tests which are currently broken at https://github.com/c42f/JuliaSyntax.jl/blob/e11f4688202debcce3600782f07b505a21ab40ec/test/parser.jl#L663-L682

I've just encountered this problem on windows 10. It seems to be independent of the python environment; I've tried the interpreter installed automatically by Conda.jl, and also manually installed via...