For the moment, this is a feature we’d love to add in, but it’s a difficult one.
The Google implementation, for example, is based upon a very large volume of past queries, so in order for this to work at the moment for us we’d have to use a 3rd party API. Doing this would come with a fair few issues of its own.
We have been reviewing our priorities again, and notably after the large survey over the last few months. It’s not a feature that many have requested there and through other channels, so other developments have taken priority. Of course, if it was a quick-win and without the issues Josh mentioned above, it could be different.