From: "Hezekiah M. Carty" <hez@0ok.org>
To: Yotam Barnoy <yotambarnoy@gmail.com>, Jeremy Yallop <yallop@gmail.com>
Cc: Hendrik Boom <hendrik@topoi.pooq.com>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Warnings opening modules (was: why is building ocaml hard?)
Date: Fri, 15 Jul 2016 19:26:14 +0000 [thread overview]
Message-ID: <CAMfPyLDsPDGvg_rCxmdacAEP8Lr=gELjT=GOJoFwYA0Myt1H+w@mail.gmail.com> (raw)
In-Reply-To: <6650375677998504317@unknownmsgid>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
type t = M.t does not bring M.t's constructors into scope. ppx_import (
https://github.com/whitequark/ppx_import) can help with this if you don't
mind preprocessing.
Hez
On Fri, Jul 15, 2016 at 2:58 PM Yotam Barnoy <yotambarnoy@gmail.com> wrote:
> Ok I have to admit that's pretty convenient.
>
> > On Jul 15, 2016, at 2:09 PM, Jeremy Yallop <yallop@gmail.com> wrote:
> >
> >> On 15 July 2016 at 17:57, Yotam Barnoy <yotambarnoy@gmail.com> wrote:
> >> In haskell, I can just say 'import A (foo, bar, baz, t)' to limit
> >> exactly what I want to import. This is because haskell has a
> >> half-baked module system that isn't nearly as powerful as OCaml's,
> >> which allows it to create syntax that doesn't need to go anywhere but
> >> at the toplevel.
> >>
> >> We need this functionality in OCaml, but the closest thing is to say
> >> 'include struct let foo = A.foo let bar = A.bar let baz = A.baz type t
> >> = A.t end'
> >
> > This can be written more succinctly:
> >
> > let foo, bar, baz = A.(foo, bar, baz)
> > type t = A.t
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2293 bytes --]
next prev parent reply other threads:[~2016-07-15 19:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 11:57 David Allsopp
2016-07-10 19:45 ` Gerd Stolpmann
2016-07-13 12:08 ` David Allsopp
2016-07-13 12:20 ` Gerd Stolpmann
2016-07-13 12:30 ` David Allsopp
2016-07-14 9:03 ` Goswin von Brederlow
2016-07-15 9:52 ` David Allsopp
2016-07-15 16:13 ` Hendrik Boom
2016-07-15 16:57 ` Yotam Barnoy
2016-07-15 18:09 ` Jeremy Yallop
2016-07-15 18:26 ` Hendrik Boom
2016-07-15 18:58 ` Yotam Barnoy
2016-07-15 19:26 ` Hezekiah M. Carty [this message]
2016-07-15 19:42 ` Yotam Barnoy
2016-07-15 19:52 ` Jeremy Yallop
2016-07-15 20:25 ` Yotam Barnoy
2016-07-15 18:50 ` Alain Frisch
2016-07-15 19:44 ` Hendrik Boom
2016-07-15 17:04 ` Gerd Stolpmann
2016-07-20 7:49 ` Louis Gesbert
2016-07-16 7:40 ` Petter A. Urkedal
2016-07-16 9:58 ` vrotaru.md
2016-07-19 16:37 ` Yotam Barnoy
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='CAMfPyLDsPDGvg_rCxmdacAEP8Lr=gELjT=GOJoFwYA0Myt1H+w@mail.gmail.com' \
--to=hez@0ok.org \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.com \
--cc=yallop@gmail.com \
--cc=yotambarnoy@gmail.com \
/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