From: Raoul Duke <raould@gmail.com>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] How to explain static typing to other people?
Date: Wed, 28 Aug 2013 12:25:31 -0700 [thread overview]
Message-ID: <CAJ7XQb4Hu8OH0x85RoKca2OO5osmt-+1v1k5R=+5b1NC6POZqQ@mail.gmail.com> (raw)
In-Reply-To: <521DEAA0.6020509@riken.jp>
> One advantage is that the OCaml (and Haskell) compilers automatically infer
> the correct type.
>
> In Java, you must always manually input the type, as far as I remember.
i was under the impression, based on personal experience as well as
hear-say, that anybody /really/ using haskell or ocaml or some such
would actually be manually entering type signatures all the time,
because they do not want to later have some incomprehensible error
that does not point to a root cause.
next prev parent reply other threads:[~2013-08-28 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:45 oliver
2013-08-28 12:18 ` Francois Berenger
2013-08-28 19:25 ` Raoul Duke [this message]
2013-08-28 19:40 ` oliver
2013-08-29 14:53 ` Florent Monnier
2013-08-29 16:00 ` Johan Grande
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='CAJ7XQb4Hu8OH0x85RoKca2OO5osmt-+1v1k5R=+5b1NC6POZqQ@mail.gmail.com' \
--to=raould@gmail.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).