Duplicate path contexts in C# extractor #7
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The pull request introduces a uniqueness check to avoid duplicate paths contexts in the C# extractor.
For an example code snippet:
I get following duplicate path contexts (adding full span of start/end syntax tokens to distinguish cases with the same token name but different location in the code snippet): [1] Is it expected behavior, or such path-contexts should be removed?
In addition, the PR suggests sampling terminal nodes in
Extractor.GetInternalPaths, before extracting the paths connecting them. The suggested sample size is 30000 - would affect only very deep/wide ASTs. Currently the Sampling down to 200 path contexts is performed on the post processing step https://github.com/tech-srl/code2vec/blob/master/preprocess.py#L23.