Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Recommenders/SnipMatch"
m (Added original paper resource) |
m (Recommenders/SnipMatch/ moved to Recommenders/SnipMatch: rm confusing slash suffix) |
(No difference)
| |
Latest revision as of 15:29, 18 March 2013
NOTE: This page is currently under construction.
Intro
TODO
User Experience
TODO
Plug-in Implementation
TODO
Next Steps
- SnipMatch currently uses a very quick and hacky solution for extracting local variables from the user's code, using code completion. This has many limitations, and is potentially inefficient. A better solution would be to extract this information directly from the AST.
- SnipMatch currently performs a web search for every query. This is inefficient. A local snippet cache could be implemented (potential student project?). This would allow search results to appear immediately, while the web search takes place in the background to search for updates.
- SnipMatch is currently not easily extensible to support other languages. A new framework could be implemented to make this easier.
External Resources
SnipMatch: Using Source Code Context to Enhance Snippet Retrieval and Parameterization [1]