From: Yawar Amin <yawar.amin@gmail.com>
To: Hendrik Boom <hendrik@topoi.pooq.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Are record types generative?
Date: Tue, 23 Jan 2018 20:56:17 -0500 [thread overview]
Message-ID: <CAJbYVJKUEAfhxH2tKgydbu=3wPuWBgYYHjK_GE6+y7Nca21MPg@mail.gmail.com> (raw)
In-Reply-To: <20180123231432.GA20089@topoi.pooq.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Hi,
On Tue, Jan 23, 2018 at 6:14 PM, Hendrik Boom <hendrik@topoi.pooq.com>
wrote:
> I'm starting to think that the ability to write OCaml programs without
> mentioning the types is a drawback in the language, because it makes
> programs hard to understand.
>
It's a tooling issue. If your editor can show you type hints and jump to
definitions on demand, you no longer have this problem. Yes, you still
can't see the types while the code is on GitHub, but that is not
insurmountable. Browser extensions nowadays are perfectly capable of
downloading and locally storing typing information and displaying it on
hover. I believe the tooling will be built when the need is acute enough.
[-- Attachment #2: Type: text/html, Size: 1098 bytes --]
next prev parent reply other threads:[~2018-01-24 1:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 14:54 Oleg
2018-01-23 16:05 ` Jeremy Yallop
2018-01-23 17:39 ` Chet Murthy
2018-01-23 20:35 ` Jeremy Yallop
2018-01-23 21:36 ` Chet Murthy
2018-01-23 22:06 ` Jeremy Yallop
2018-01-23 23:14 ` Hendrik Boom
2018-01-24 1:06 ` Chet Murthy
2018-01-24 1:35 ` Francois BERENGER
2018-02-07 2:00 ` [Caml-list] [ANN] first release of bst: a bisector tree implementation Francois BERENGER
2018-02-07 12:40 ` Ivan Gotovchits
2018-02-08 0:46 ` Francois BERENGER
2018-01-24 1:56 ` Yawar Amin [this message]
2018-01-25 10:49 ` [Caml-list] Are record types generative? Matej Košík
2018-01-25 13:39 ` Simon Cruanes
2018-01-25 16:24 ` Yawar Amin
2018-01-24 1:05 ` Chet Murthy
2018-01-24 8:43 ` Jacques Garrigue
2018-02-02 23:07 ` Toby Kelsey
2018-02-02 23:23 ` Evgeny Roubinchtein
2018-02-04 1:27 ` Jacques Garrigue
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='CAJbYVJKUEAfhxH2tKgydbu=3wPuWBgYYHjK_GE6+y7Nca21MPg@mail.gmail.com' \
--to=yawar.amin@gmail.com \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.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;
as well as URLs for NNTP newsgroup(s).