My first thought was "I hope I never encounter code that uses this." It's interesting as a proof of concept, but it makes your R code difficult to understand to 99.9% of R programmers. In my opinion, that is a pretty high cost for what I would consider mostly syntactic sugar.
That said, a lot of the use-case of R is one-off scripts, run locally on a machine by an analyst, as part of preparing a written report for non-technical stakeholders. So the code readability isn't as important.
This is both a strength and weakness of R in general. The R community has many different ways to accomplish the same goals. Production systems decline to use R in large part because of the code maintenance burden across a team, versus Python's "one right way" approach.
Does it come down more to an agreement among the team about how code should be written?
The author is an interesting guy. He has lots of ideas about R, but seems to have spread himself a bit too thin and so he doesn't really finish them. This package is one example, but he also was in the middle of writing two nice books about R [1] [2], and they are still in limbo.
[1]: https://cartesianfaith.com/2017/04/14/modeling-data-with-fun...
[2]: https://cartesianfaith.com/2018/11/12/preview-my-new-book-in...