<blockquote>
<p>Seems like some extraneous function definition is being made for the calltip. But it never appears in the symbol list.</p>
</blockquote>

<p>Actually it does: when you don't have the <code>(</code> yet, the parser extracts <code>ns::C::f (junk, rubbish)</code>.  Apparently it's the <code>public:</code> part that confuses it the most, if you drop it you don't get the erroneous <code>f</code> function.  So yeah it's not great, but fixing that would require getting the parser not confused by this particular invalid input.</p>

<blockquote>
<p>And ... if there happen to be other functions named <code>f</code> the calltips will cycle through the prototypes of those functions and never come back to the erroneous one.</p>
</blockquote>

<p>That's a "funny" side effect of the details of the issue: once you typed the <code>(</code>, the parser doesn't see a <code>f</code> any more; and when you cycle through the calltips, apparently (?) we query the possible candidates again, so at this point we don't find the erroneous <code>ns::C::f</code> as the parser doesn't report it anymore.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1249#issuecomment-250686071">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJyXrLmWgIu0EiX3TcfgJ_-ElPi7Aks5qvMSRgaJpZM4KK0LK">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJwqeaDsIX0zLBUIFef8nZAs3P9VVks5qvMSRgaJpZM4KK0LK.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1249#issuecomment-250686071"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@b4n in #1249: \u003e Seems like some extraneous function definition is being made for the calltip. But it never appears in the symbol list.\r\n\r\nActually it does: when you don't have the `(` yet, the parser extracts `ns::C::f (junk, rubbish)`.  Apparently it's the `public:` part that confuses it the most, if you drop it you don't get the erroneous `f` function.  So yeah it's not great, but fixing that would require getting the parser not confused by this particular invalid input.\r\n\r\n\u003e And ... if there happen to be other functions named `f` the calltips will cycle through the prototypes of those functions and never come back to the erroneous one.\r\n\r\nThat's a \"funny\" side effect of the details of the issue: once you typed the `(`, the parser doesn't see a `f` any more; and when you cycle through the calltips, apparently (?) we query the possible candidates again, so at this point we don't find the erroneous `ns::C::f` as the parser doesn't report it anymore."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1249#issuecomment-250686071"}}}</script>