Kirill Müller

Is it sufficient to search the code for `getRversion()` to find all workarounds?

Could be on by default, works for me except for the output of incomplete lines (to indicate progress). I think we can solve this by printing complete lines after completion...

Not yet.

Thanks. If we just reversed the rows of `pd$child[[1]]` (except `id` which we'd leave untouched) and changed `RIGHT_...` to `LEFT_...`? Do the nests refer to parent IDs in any way?...

It seems that connecting `function()` to its definition has lower precedence than `->` in R's parser: ``` r body(function() {} -> f) #> f } body(f { #> } ```...

I don't think we need to take any action here: you can't define a function with right assignment. ``` r function() {} -> f #> function() {} -> f f...

I see a problem when simply reversing `lhs lhs` isn't equivalent for the parser. The function example is an important one, are there others? ``` r styler:::create_tree("f f") #> levelName...

@gmbecker: I'm comparing `f f` . These two are parsed differently. If we only reverse `->` towards `

Thanks. I agree profiling should be the first step. There are four steps: - Parsing (done by base R, should be fast enough) - Nesting of parse data (`compute_parse_data_nested()`) -...

I took another look at styling performance. With the two new PRs combined, and when replacing `%>%` with `|>`, we now finally get usable stack traces when profiling. With `proffer::pprof(filter.callframes...