[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 183614] Code completition inside template specialization not
From:       "Olivier.jg" <olivier.jg () gmail ! com>
Date:       2009-12-01 6:30:30
Message-ID: 20091201063030.8653E286F4 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=183614


Olivier.jg <olivier.jg@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olivier.jg@gmail.com




--- Comment #2 from Olivier.jg <olivier jg gmail com>  2009-12-01 07:29:06 ---
FunctionContexts seem to operate on the assumption that for every declaration
there is one definition. Since the template allows any number of additional
definitions for any given declaration, any definitions after the first have no
mapping to the declaration, therefore it's unable to find the class context it
that the function belongs to.
As far as I can tell, the only reason it works without the "this" is because it
then gets to MissingIncludeCompletion.
So a dirty little hack would be to detect this happenstance and give it
MissingIncludeCompletion, but to fix the real underlying problem could mean a
healthy amount of work, affecting much of the cpp support (in particular I'm
thinking of the cpp codegen codeassistant, but the real implications are
unknown to me).
I might be interested in chewing on the full solution when I have a larger
chunk of time, but should that even happen in this release? Is a dirty hack
better for now? Or perhaps not consider this bug a 4.0.0 target?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]