The primary use case I experience for searching for idiomatic usage patterns is to know how to do a higher level refactoring, meaning I don’t want results that have syntax tree similarity to what I’ve got or even the small bit I start from to create the query. I want the <i>intention</i> of my search query but expressed in a better design.<p>Separately, for very micro-level idiomatic things, like use of a certain data type operation or efficient constructor patterns, I need to search by natural language descriptions of the subtle differences between options. This is what makes Stack Overflow so helpful, the accompanying natural language description of intentionality or special cases, even if the code that is found isn’t precisely what’s needed, it demonstrates <i>directionally</i> what to do.<p>This tool seems like yet another example of trying to force machine learning solutions to problems nobody actually has.<p>Considering the idea that I’d need to integrate this into my coding environment, I’ll say No Thanks!