caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Peter Zotov <whitequark@whitequark.org>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ppx_deriving 0.1
Date: Wed, 23 Jul 2014 16:37:20 -0400	[thread overview]
Message-ID: <CAN6ygOn9DfeSAS4=_Sh3ZPEpyWmo0Hwrt=dRL3C6X95+HnUP6w@mail.gmail.com> (raw)
In-Reply-To: <e80703f7323f3e72b345836b5e48927e@whitequark.org>

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

OK, I was just making some suggestions based on experience I have with
haskell's deriving, which I use all the time, and trying to bring as much
of that ease of use as possible to ocaml.

Any idea where I can find some info on ocaml's upcoming implicits? A google
search was not particularly helpful.



On Wed, Jul 23, 2014 at 4:19 PM, Peter Zotov <whitequark@whitequark.org>
wrote:

> On 2014-07-23 18:36, Yotam Barnoy wrote:
>
>> Very nice.
>>
>> I've never used any of the deriving extensions before, but I have an
>> aesthetic suggestions.
>>
>
> I humbly suggest trying to use it before proposing aesthetic changes.
>
>
>  Would it perhaps make sense to generate a
>> module per derived type? For example a type t would generate a module
>> T_ (the underscore or any other suffix would reduce mixups with
>> pre-existing modules). You could then use code such as
>>
>> 'if T_.(a = b && b = c) ...'
>>
>> or  'T_.show x ...'
>>
>> which allows you to keep the infix notation for = which is important
>> IMO.
>>
>> You could even generate T_ as having internal Eq, Ord, and Show
>> modules (as requested by the user), which would be included in the T_
>> module. This would allow you to easily pass them as first class
>> modules to functions accepting Eq, Ord or Show signatures.
>>
>
> I believe this is best left to the upcoming implicits, which will
> hopefully be merged soon.
>
> I have based the current design on existing patterns across OCaml
> ecosystem; I don't want to change the way people structure their
> modules, I want to reduce the amount of boilerplate to write.
>
>
> --
> Peter Zotov
> sip:whitequark@sipnet.ru
>

[-- Attachment #2: Type: text/html, Size: 2501 bytes --]

  reply	other threads:[~2014-07-23 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  9:55 Peter Zotov
2014-07-23 14:36 ` Yotam Barnoy
2014-07-23 20:19   ` Peter Zotov
2014-07-23 20:37     ` Yotam Barnoy [this message]
2014-07-28 12:26       ` Peter Zotov

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='CAN6ygOn9DfeSAS4=_Sh3ZPEpyWmo0Hwrt=dRL3C6X95+HnUP6w@mail.gmail.com' \
    --to=yotambarnoy@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=whitequark@whitequark.org \
    /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).