Issued with Clion Inspection Resolution since 2018.1

[trivigy]

Really not sure how to touch base with clion nor do I feel like they will do anything to fix this. Figured I will post it here and see if anyone else has the same issue.

In both cases I am getting: "no matching function" and "no matching constructor".

However the code compiles and works fine.

[nlohmann]

This is strange. But CLion seems to have some issues with templates. It keeps proposing to "optimize" the code by removing SFINAE guards. I am not sure whether CLion has a bug tracker, but I think opening an issue there could help.

[trivigy]

Raised an issue on clion board. Hopefully someone on their end will look into this. One other thing I mentioned was that I noticed an update in clang version along with the upgrade to clion-2018.1. Could it be related to clang changing something? I believe inspection is done using clang, I may be wrong on that one though.

https://youtrack.jetbrains.com/issue/CPP-12558

[nlohmann]

Thanks for reporting! If the inspection worked before, then it could really be a Clang bug as well.

[nlohmann]

The issue could be fixed with CLion 2018.1.1 EAP, see https://youtrack.jetbrains.com/issue/CPP-12558.

[trivigy]

I can confirm that it fixes it partially. My guess that this will get totally fixed in the next release. I also was right, this has to do with clang-tidy. I can see a slightly different issue now but I will keep following up on this with the jetbrains team. This thread can probably be closed.

[nlohmann]

Thanks a lot for reporting! I'll do my best that this library can serve as a benchmark for Jetbrains ;-)

[trivigy]

@nlohmann Don't be harsh on yourself. You are already doing an absolutely amazing job. I tried tons of json libraries and finally stuck with this because of the awesome syntax you made work. I am sure implementing that was not easy. So, it is bound to have some issues with the jetbrains coding style and expectations.

[OvermindDL1]

For note, I tried the code in KDevelop (which also embeds clang) and it did not have such issues, so it's not a clang thing. :-)