I'm using a custom comparison function with Pebble (main reason is to have hierarchical friendly sorting, eg. assigning special meaning to / and have filesystem like tree structure).

This worked well in Pebble 1.x (apart from the addition of AbbreviatedKey which silently broker the ordering.. :) ).

In Pebble 2.1 there is an assertion check the custom compare returns the same order as the default compare:

Is there anything I'm missing here? Any configuration function to pass in to make it work? How any non-standard compare implementation can work if it needs to be checked against bytewise compare in the end?

Jira issue: PEBBLE-1217