caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Pierre Weis <Pierre.Weis@inria.fr>
To: monnier+lists.caml/news/@RUM.cs.yale.edu (Stefan Monnier)
Cc: caml-list@inria.fr
Subject: Re: Functions must be explicitly typed, (was Same label in different types, how do people solve this?)
Date: Fri, 15 Dec 2000 13:47:24 +0100 (MET)	[thread overview]
Message-ID: <200012151247.NAA30942@pauillac.inria.fr> (raw)
In-Reply-To: <5lpuiuzvy9.fsf@rum.cs.yale.edu> from Stefan Monnier at "Dec 14, 100 01:42:06 pm"

> >>>>> "Mattias" == Mattias Waldau <mattias.waldau@abc.se> writes:
> > I don't really see the use of infering types for functions. It works for one

I would like to note that type inference (i.e. code without
annotations) helps a lot when developing programs: the annotation free
code is not only easier to write but also easier to maintain since it
is kind of ``auto-adaptative'' and resistant to reorganisations and
names modifications.

As an example, consider a function with an explicit profile:

let (type_type_definition : Synt.td -> ...) = function ...

If we consider renaming the module Synt into Syntax, and the type td
into type_definition to reflect as closely as possible the intended
meanings, we would have to edit the definition of the function (and
the definition of every function that uses either the module Synt or
the type td). By contrast, if we omit manual type annotations, the
type checker will silently change the type assigments as necessary. It
is extremely convenient when writing systems that are rapidly
evolving.

Hope this helps,

Pierre Weis

INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://cristal.inria.fr/~weis/




  reply	other threads:[~2000-12-15 12:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 21:22 Same label in different types, how do people solve this? Mattias Waldau
2000-12-07 16:49 ` John Max Skaller
2000-12-07 18:34 ` Maxence Guesdon
2000-12-07 23:02 ` Gerd Stolpmann
2000-12-08  1:22 ` Jacques Garrigue
2000-12-08  9:31   ` Sven LUTHER
2000-12-08  9:36     ` Pierre Weis
2000-12-08  9:48       ` Sven LUTHER
2000-12-08 18:41       ` John Max Skaller
2000-12-08  9:40     ` Nicolas barnier
2000-12-08 16:36 ` Brian Rogoff
2000-12-11 17:19   ` Pierre Weis
2000-12-10 12:49 ` Mattias Waldau
2000-12-11 18:23   ` Chris Hecker
2000-12-11 19:17     ` Pierre Weis
2000-12-12 10:02       ` Sven LUTHER
2000-12-12  3:25     ` Chet Murthy
2000-12-12 17:43       ` John Max Skaller
2000-12-12 19:24         ` Functions must be explicitly typed, (was Same label in different types, how do people solve this?) Mattias Waldau
2000-12-13  0:51           ` John Max Skaller
2000-12-15 10:13             ` Andreas Rossberg
2000-12-15 12:50             ` Frank Atanassow
2000-12-14 18:42           ` Stefan Monnier
2000-12-15 12:47             ` Pierre Weis [this message]
2000-12-15 13:39               ` Mattias Waldau
2000-12-15 23:37                 ` Brian Rogoff
2000-12-16 14:10                 ` ROverloading John Max Skaller
2000-12-15 21:51         ` Same label in different types, how do people solve this? Bruce Hoult
2000-12-12 17:19   ` John Max Skaller

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=200012151247.NAA30942@pauillac.inria.fr \
    --to=pierre.weis@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=monnier+lists.caml/news/@RUM.cs.yale.edu \
    /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).