Great to hear!
Am 12.12.18 um 00:11 schrieb Mateusz Loskot via cfe-users:
>> I suspect that is the case indeed.
>>
>> I have created new test in GIL which generates single .cpp file
>> that includes all headers (https://github.com/boostorg/gil/pull/184):
>> I generated compile_commands.json and ma
On Mon, 10 Dec 2018 at 22:25, Jonas Toth wrote:
> Am 10.12.18 um 22:14 schrieb Mateusz Loskot via cfe-users:
> >
> > Why clang-tidy tries to re-fix the typedef with new replacement
> > instead of keeping the existing one, the generic one?
>
> Maybe a bug that does not handle some possible cases we
Hi Mateusz,
comments inline.
Am 10.12.18 um 22:14 schrieb Mateusz Loskot via cfe-users:
> Hi,
>
> I'm running clang-tidy 7.0 (also tried 5.0) to modernise some aspects
> of Boost.GIL (https://github.com/boostorg/gil) source code.
>
> I've noticed, clang-tidy 7.0 (also 5.0) does not apply fixes fo
Hi,
I'm running clang-tidy 7.0 (also tried 5.0) to modernise some aspects
of Boost.GIL (https://github.com/boostorg/gil) source code.
I've noticed, clang-tidy 7.0 (also 5.0) does not apply fixes for some of
modernize-use-* checks, especially modernize-use-using.
I run it this way:
```
cd ${BOOS
