- Consistify by index order when sorting coalesced sets.
- Use a forward and reverse getsetrelevance analysis to handle addresses.
Merge branch 'master' of github.com:mapbox/carmen into relev-reverse
Reversed relev sort should only reverse index comparison.
Merge branch 'test-better' into relev-reverse

Conflicts:
	lib/spatialmatch.js
Merge branch 'test-better' into relev-reverse
More stringent corner cases tests and refactored spatialmatch to pass 'em.
Reintroduce rowMemo concept to dedupe results for identical features.
Nuke setrelevance penalty for gaps between indexes in matching results.
Update test fixtures - South Korea drops was making it through to context verification because of an inflated spatialmatch score in master.
Revert "Nuke setrelevance penalty for gaps between indexes in matching results."

This reverts commit c3a1439973d72e5c0047f71162759d4914d352d5.
Reintroduce gap penalty, take the hit on windsor ct for now ...
Back off on trying to solve windsor ct case right now.
Update tests to confirm first-in-hierarchy priority is preserved amongst ties.
Only retain elements in sets for same indexes if they have equivalent reason for matching.
Add test for setrelevance stack mutation.
More comments.
Merge branch 'master' into relev-reverse
Merge branch 'master' into relev-reverse
Merge branch 'master' into relev-reverse
Merge pull request #140 from mapbox/relev-reverse

Spatialmatch relevance sort refactor