Claire Foster

`fl_parse` is just a direct call to the reference parser. It's useful when developing this library to use instead of `Meta.parse()`, as `Meta.parse()` may have been overridden with the newer...

I chatted to @JeffBezanson about a couple more of these issues today. We thought that * The current behavior of JuliaSyntax handling of edge cases in triple quoted string deindentation...

Ok, so this is related to the logic at https://github.com/JuliaLang/JuliaSyntax.jl/blob/acb609d803379df6b003133d81884c7e8314ac90/src/expr.jl#L287-L289 I think the subtle point here is that the right hand side of `.` should always be inert: that is,...

This syntax was found in the General registry in Accessors.jl and Setfield.jl (the predecessor package of accessors). But in these cases the syntax was only used in a test case...

Hi @gafter, thanks for taking the time to comment! Currently diagnostics (errors/warnings/etc) are not a side effect of the parser - they are returned as a result of parsing and...

It was meant to implement the flavor of the original proposal, more or less (but I've also added some underscore processing which is clearly unrelated). Think of this as a...

Noting that this syntax can be used without data on the left hand side to create a first class data pipeline, I've upgraded this to allow syntax such as h...

Thanks! ``` # front pipe: a \> f(b, c) # parses as f(a, b, c) ``` A quibble: we wouldn't parse it this way because an important feature of the...

So, it turns out that the lowering adopted here can provide fundamentally more efficient data pipelines than normal piping by allowing rewrite rules to be added as methods to `chain`....

> more efficient data pipelines than normal piping by allowing rewrite rules to be added as methods to `chain` Though rewrite rules are a symbolic simplification step which is not...