Closed MilesMcBain closed 3 years ago
Thanks for the nudge! I'll try to implement this soon.
Looks like I did implement this a while back:
https://github.com/kevinushey/sourcetools/commit/8827fa5dff46865bfc9603ef3f656c2f71e0fa95
So, with the development version of sourcetools
, I see:
> sourcetools::tokenize_string("1 |> I()")
value row column type
1 1 1 1 number
2 1 2 whitespace
3 |> 1 3 operator
4 1 5 whitespace
5 I 1 6 symbol
6 ( 1 7 bracket
7 ) 1 8 bracket
Can you confirm?
Hi @kevinushey
I am interested in any plans to change the way
{sourcetools}
parses tokens for the new|>
operator.Right now we have:
Which is actually not too bad since it is fairly easy to transform that:
polyfill_base_pipe()
is a function I have in{breakerofchains}
, which is a revdep of{sourcetools}
that is not on CRAN at the moment.If you are planning to update the tokenizer for this syntax is there something I could follow to track the progress of that?
Thanks, Miles