[mercury-users] Wishes for 0.13.1

[doug.auclair at logicaltypes.com]

Dear Julien,

If you will be adding rtree to 0.13.1 (which I hope you do, as I am now using it
quite a bit), I have a small ordering request:  one of the provided types, box3d,
has this ordering:

box3d(xmin, xmax, ymin, ymax, zmin, zmax).

I understand the implementation point, but, declaratively, it's weird.  I expected
a box to be defined thus:

box3d(xmin, ymin, zmin, xmax, ymax, zmax).

and have run into logic errors in my programs when I trip up on my disconnect.

If there are no objections, could the definition of box3d be changed to the latter?
(The declaration is unchanged).

If the same setup exists for the 'box' type, could the same implementation change
occur?

Thank you.

Sincerely,
Doug Auclair

--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------