Takafumi Arakaki

IIUC there is no magic in `clang-format-diff.py`. It just uses VCS' `diff` command to construct `--lines` options passed to `clang-format` ``` --lines= - : - format a range of lines...

FYI, I just found https://github.com/reviewdog/action-suggester which can be used to suggest formatting for the parts of the code that the PR touches. See https://github.com/tkf/Try.jl/pull/21 for an example setup. See https://github.com/tkf/Try.jl/pull/22...

Thanks for the explanation. It sounds challenging when you have different associativity and also ChainOpCall. By the way, I think something like ```julia function _() return some_expression * some_expression *...

Yeah, I can imagine that it would be a very hairy thing to write...

I have a working CLI based on RPC to avoid any JIT overhead. My aim is to use JuliaFormatter.jl via https://pre-commit.com/ framework. I'll put it on github soon.

I put very minimal installation guide in: https://github.com/tkf/JuliaCLI.jl

Yeah, I think this is expected: ```julia julia> code = """ f( \"\"\" string \"\"\", \"\"\" string \"\"\", ) """; julia> print(code) f( """ string """, """ string """, )...

My workaround ATM is to put some comments inside: ```julia julia> code = """ f( # workaround "a" => \"\"\" string \"\"\", "b" => \"\"\" string \"\"\", ) """; julia>...

@m2ym Do you think this should be solved before v0.5?

The motivation is for automating interface compatibility test. This, in turn, requires a way to find out what interface is supported by a given type. For example, let's say you'd...