Hi
Stef, thanks for the paper, i'll check it out. I agree that there's many cool things that can be still done statistically, but the ML/NLP approach should be worth trying out, too. Maybe it will give good results, maybe it will turn out to be not applicable to Pharo for whatever reason... But the point is that now the code completion architecture is definitely simpler and more scalable, and especially because of the sorter plugin it will be easy to work on any sorting strategy and then make it one of the options. There's indeed a lot of work that can be done in measuring different strategies and seeing what works better as there's still not *that* much research on the topic.
Tudor and Cris, yeah i haven't really worked with Spec in a while but i get what you mean. I agree it would be great to have that! There's still tons and tons of improvements that could be made, as you say, regarding completing larger templates, but also doing convenient tab usage for jumping between parts of larger templates or even for things like ifTrue:ifFalse:, possible snippet (method name shorthand) completion, etc etc. I'm always happy to extend the todo list haha. Oh and FYI, at ESUG on friday at noon Marcus and i will be doing a presentation about what's been done and also what we want to do in the nearest future so i hope some people stick around even though it's the last day :)
Best,
Myroslava