From: "Robert Fischer" <RFischer@RoomAndBoard.com>
To: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] F#
Date: Thu, 8 Mar 2007 08:41:09 -0600 [thread overview]
Message-ID: <3D1E4D9CA9BCE04D8F2B55F203AE4CE30666AB5E@selma.roomandboard.com> (raw)
> However, operator overloading (i.e. overloading symbols) makes numerical code
> so much easier to read that it is worth sacrificing some inference for it.
>
Unless, of course, you like to know what it is you're actually doing.
It's bad enough trying to figure out what "+" means in an overloaded environment with nominal typing. With duck typing, it's a mess, and it's a mess that both you and the compiler have to work hard to figure out.
I highly suggest checking out the Programmer-to-Programmer book on C# and their conversation about operator overloading. They do a nice job documenting just why it's such a dangerous tool in the toolbox.
~~ Robert.
next reply other threads:[~2007-03-08 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 14:41 Robert Fischer [this message]
2007-03-08 15:10 ` Jon Harrop
2007-03-08 17:30 ` Roland Zumkeller
2007-03-08 17:54 ` Brian Hurt
2007-03-08 19:40 ` [Caml-list] Operator overloading Jon Harrop
2007-03-08 20:44 ` Brian Hurt
2007-03-08 22:24 ` Fernando Alegre
2007-03-08 23:07 ` [Caml-list] F# skaller
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 1:13 Interactive technical computing Jon Harrop
2007-03-08 2:12 ` [Caml-list] " Erik de Castro Lopo
2007-03-08 12:41 ` [Caml-list] F# Jon Harrop
2002-06-10 14:04 Don Syme
[not found] <BCDB2C3F59F5744EBE37C715D66E779C0481E208@red-msg-04.redmon d.corp.microsoft.com>
2002-06-09 17:49 ` Chris Hecker
2002-06-09 12:26 Don Syme
2002-06-10 6:22 ` Michael Vanier
[not found] <BCDB2C3F59F5744EBE37C715D66E779C0481E206@red-msg-04.redmon d.corp.microsoft.com>
2002-06-09 1:30 ` Chris Hecker
2002-06-08 23:04 Don Syme
2002-06-08 15:05 Vincent Foley
2002-06-08 16:01 ` Xavier Leroy
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=3D1E4D9CA9BCE04D8F2B55F203AE4CE30666AB5E@selma.roomandboard.com \
--to=rfischer@roomandboard.com \
--cc=caml-list@yquem.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).