Bug 337971 - Semantic analysis incorrectly matches ctor
Summary: Semantic analysis incorrectly matches ctor
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: git master
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-02 00:19 UTC by Mikael Öhman
Modified: 2018-03-25 22:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Minimal example showcasing bug in Kdevelops cpp plugin (244 bytes, text/x-c++src)
2014-08-02 00:19 UTC, Mikael Öhman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael Öhman 2014-08-02 00:19:23 UTC
Created attachment 88082 [details]
Minimal example showcasing bug in Kdevelops cpp plugin

When calling a ctor like  "MyArray x{123};" or "MyArray{123}", the initializer_list ctor takes precedence if it is available in the class.

In the attached minimal example, KDevelops semantic analysis incorrectly thinks that I'm trying to call the deleted function when i write "MyArray{1}", and gives the error:
Problem in Semantic analysis:
Use of deleted function: MyArray
Comment 1 Kevin Funk 2018-03-25 22:48:03 UTC
Hello!

We are working on a new clang-based C/C++ language plugin for KDevelop 5 which
supersedes the old C++ plugin in KDevelop 4. See e.g.:
https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available

Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather
want to supply a good Clang based C++ experience for KDevelop 5 than wasting
our time on the legacy C++ support for KDevelop 4.

With the new clang-based C/C++ language plugin, the bug presented here does not
occur. In my testing. For these reasons, I'll close this bug. Please stay tuned
for KDevelop 5.

If you think this bug is applicable to Clang/KDevelop 5, please reopen the
report and add new information on how to reproduce the bug there.