Re: Proposal for containers: Add 'lookup' function to Data.Set

Hi, given that for naive uses and users, the existence of lookup is more confusing than helpful, I’m in favor of a name that indicates “this is advanced foo”, a suitable documentation, and moving it to the very end of the module documentation, as it is not a function you’d expect for a set implementation. The name "Pointer", though, might be a bit too low-level. Maybe "lookupWithSharing"? Greetings, Joachim Am Dienstag, den 28.06.2016, 06:14 +0100 schrieb Malcolm Wallace:

Or "lookupSharedPointer", if that is the important part of the operational semantics.

 Regards,     Malcolm (iPhone)

On 27 Jun 2016, at 23:17, David Feuer wrote:

Another option might be "find". On Jun 27, 2016 5:56 PM, "David Feuer" wrote:

...

As much as I dislike the names lookupGT, et al, I think that's probably your best bet now that they exist. On Jun 27, 2016 5:52 PM, "Nicolas Godbout" wrote:

...

David Feuer wrote:

...

+1 on the function. -1/2 on the name.

To be honest, I briefly considered the name `lookupEQ`. The name would fit nicely with `lookupGT` and company.

Nicolas.

-- Joachim “nomeata” Breitner   mail@joachim-breitner.de • https://www.joachim-breitner.de/   XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F   Debian Developer: nomeata@debian.org