Always build "what" from the original tokens.

We were already using the original tokens when a connector is present.
We now use the original tokens for connector-less queries, too.
simplify(?) comparator function and use near float equality

maybe this is causing instability?

hopefully a no-op.

Auditors: rahul, nsanch
I'm an idiot, ints are equal
fix tests
stop using custom ivy path
two small perf spots that might have synchronization issues
Revert "fix bounds distance"

something in this s2 logic slowed the server to a crawl?

This reverts commit 2a18fc8a80ead2fdf90224902a9471fca71c5044.
.17 bump for ll/bounds exception

Auditors: rahul, nsanch
kill shinjuku alias on tokyo
Merge branch 'master' of github.com:foursquare/twofishes
fix bad poly detection code

This code still thinks the polygon index is keyed off the feature id. Also,
finally kill reference to polygon field on the feature index. I've checked in
mongo and no document has it.

Auditors: blackmad, nsanch
Minor bug fix

Hitting enter to submit form sends lookup=<slug> param rather than slug=<slug>

Auditors: blackmad
distanceFromPointToBounds fix

Auditors: nsanch, blackmad
Fix shorten parsing and logic

Shorten only at word boundaries
Also, we currently do not correctly parse shortenTo. Incidentally, although the
documentation mentions that flags can be specified, no attempt is made to parse
them. We still don't know how to use them (since shortens automatically get the
SHORT_NAME flag) but that's a separate issue.

Auditors: blackmad, nsanch
Add distance buckets to scoring

Auditors: nsanch, blackmad
Code review feedback

Auditors: blackmad
bumping up twofishes version

Auditors: blackmad
increase max # of prefix matches

washington was ~2025

Auditors: rahul
scoring redesign

GeocodeParseOrdering can be customized by passing in a list of scoring functions
with weight multipliers so that geocode and autocomplete scoring can reuse the
same scoring functions but weight them differently.

Also, tweak distance buckets a bit.

Geocode scoring should be largely unaffected by the change. The weights have been
fine tuned for autocomplete alone.

Auditors: nsanch, blackmad
Show latlng hint on map for autocomplete

Auditors: blackmad