From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Ben Millwood <bmillwood@janestreet.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Specify the default hash function for a type
Date: Fri, 13 May 2016 08:40:49 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CEF1721@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CA+MHO530ccscg4vYdrFHoM8s-b6+Yf7ZtoyQQUvpY4Gj2VsXJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Dear Ben,
thanks a lot for the quick answer! I am looking forward to the PPX.
Best regards,
Michael
From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf Of Ben Millwood
Sent: Friday, May 13, 2016 10:14 AM
To: Soegtrop, Michael
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Specify the default hash function for a type
Polymorphic hash operates without type information, so it's not able to tell that it's hashing your record type vs. some other type with the same structure. So I would guess that what you want is not possible.
The Core team is working on a ppx extension analogous to ppx_sexp_conv and ppx_compare which generates hash functions automatically, and would make this kind of thing possible, but it's not done yet.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
[-- Attachment #2: Type: text/html, Size: 4807 bytes --]
next prev parent reply other threads:[~2016-05-13 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 7:52 Soegtrop, Michael
2016-05-13 8:13 ` Ben Millwood
2016-05-13 8:40 ` Soegtrop, Michael [this message]
2016-05-13 9:06 ` Alain Frisch
2016-05-13 9:26 ` Soegtrop, Michael
2016-05-13 12:01 ` Gabriel Scherer
2016-05-13 12:23 ` Alain Frisch
2016-05-13 12:32 ` Soegtrop, Michael
2016-05-13 13:50 ` Pierre Chambart
2016-05-13 13:56 ` Alain Frisch
2016-05-13 16:17 ` Soegtrop, Michael
2016-05-13 18:57 ` Thomas Braibant
2016-05-13 22:45 ` Soegtrop, Michael
2016-05-14 8:41 ` Thomas Braibant
2016-05-14 9:06 ` Soegtrop, Michael
2016-05-17 13:03 ` Soegtrop, Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F7D3B1B3C4B894D824F5B822E3E5A172CEF1721@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=bmillwood@janestreet.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).