Incorrect definition highlighting in for different scopes about nvim-treesitter HOT 4 CLOSED

@theHamsta , I don't really agree with that, in the case of functions for example, you can find the definition of that function below the cursor (for example in Rust).
Regarding the fact it finds things somewhere else is quite weird, as it should only go upwards in scope hierarchy, that needs a bit of investigation.

from nvim-treesitter.

@vigoux It may be. I need to look into a little bit further.

from nvim-treesitter.

Sorry deleted the coment, but it might be related to locals.

from nvim-treesitter.

I think the find_definition should always find declarations before the current cursor position.

Consider the following example:

void normalReactionTest(cr::HCSITS& cr, SphereID sp)
{
   contactThreshold = Thresholds<real_t>::contactThreshold();
   // plane at 5,5,5
   // radius 1.1
   sp->setPosition(  Vec3(5,5,6) );
   sp->setLinearVel( Vec3(0,0,0) );
   cr.setErrorReductionParameter( real_t(1.0) ); // <----------------- cursor at beginning of line
   cr.timestep( real_c( real_t(1.0) ) );
}

int main( int argc, char** argv )
{
   cr::HCSITS cr(globalBodyStorage, forest->getBlockStoragePointer(), storageID, hccdID, fcdID); // <-- will find this definition
   return EXIT_SUCCESS;
}
} // namespace walberla

Without #145 it can't recognize the definition of cr as an arguments and finds cr in a completely different scope (no ideas why it can find stuff from a different scope)

from nvim-treesitter.