If the maintenance cost of
keeping both options in the Clojure run
time is reasonnable it's fine with me.
Rich is the best person to answer this.
Otherwise, auto promotion should be
the winner... And the default ...
The vast majority of apps these days
are not gravitating around high
performance numeric computations.
Forcing people to deal with this in mundane code would be insane
in the long run.
Reminds me of C in the early days when we needed to keep and eye on
what was a byte, a short, an int
or a long on the different hardware platforms...
If we want Clojure to remain a viable
option lets keep some usage simplicity
a primary goal.
When I want to scratch every bit of
performance, I expect to kick my butt
out to get it but after I have some
working code running, not while I scratch my head about getting it done.
Proposals up to know regarding
specific operators for various
implementations provide plenty of
options to attain the nirvana of
high performance. That's good.
Lets just make things easy for the
average guy..,
Luc P
Sent from my iPod
On 2010-06-22, at 7:53 AM, Nicolas Oury <nicolas.o...@gmail.com> wrote:
On Tue, Jun 22, 2010 at 12:45 PM, Luc Préfontaine <lprefonta...@softaddicts.c
a> wrote:
Data changes overtime and
discovering it in production with
an overflow exception is less than
elegant.
Degraded performance is much more
acceptable in production than a crash
over an unhandled exception ....
Depends in which production.
That's why I defend a way to choose default.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient
with your first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
