caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Damien Doligez <damien.doligez@inria.fr>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] About contributions to the Standard Library
Date: Thu, 30 Jun 2016 12:59:21 +0200	[thread overview]
Message-ID: <20160630105920.GA16808@frosties> (raw)
In-Reply-To: <1467026350.6080.9.camel@e130.lan.sumadev.de>

On Mon, Jun 27, 2016 at 01:19:10PM +0200, Gerd Stolpmann wrote:
> Am Montag, den 27.06.2016, 11:09 +0200 schrieb Goswin von Brederlow:
> > Why should we contribute when contibutions are just left to bitrot?
> > 
> > Like: http://caml.inria.fr/mantis/view.php?id=4909 which has had a
> > patch for 6 1/2 year that's just left rotting.
> 
> I guess you hit one of the pain points of the current library design,
> namely the various integer types (and the issue of combinatorial
> increase of possible variants). In my most recent code (a data science
> lib) I solved that radically - no support for 32 bit architectures
> anymore. The truth is that with current OCaml you cannot support both 32
> bit and 64 bit equally well. Either you get a performance loss from
> boxed ints, or you get macros in central places of your code.
> 
> Of course, that's no excuse for not responding at all.
> 
> Gerd

But that patch addresses exactly that problem by introducing a new
Bigarray type that is fast (uses int, not a boxed type) and also uses
the same size on 32bit and 64bit. There are many cases where 31bit
integers are sufficient but in ocaml one can not use them consistently
on 32bit and 64bit.

MfG
	Goswin

      parent reply	other threads:[~2016-06-30 10:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 11:56 Damien Doligez
2016-06-21 15:48 ` Gabriel Scherer
2016-06-21 15:54   ` [Caml-list] About "precise (formal) things that can be said about properties of certain interfaces" David MENTRE
2016-06-21 19:11     ` Gabriel Scherer
2016-06-21 20:06       ` Jesper Louis Andersen
2016-06-22 15:33   ` [Caml-list] About contributions to the Standard Library Junsong Li
2016-06-22 21:31   ` Alain Frisch
2016-07-07 10:26   ` Daniel Bünzli
2016-07-08 14:01     ` Alain Frisch
2016-07-08 14:37       ` Daniel Bünzli
2016-07-11  8:55         ` Goswin von Brederlow
2016-07-11  9:43           ` Daniel Bünzli
2016-07-11  9:48             ` Adrien Nader
2016-07-11 10:28               ` Daniel Bünzli
2016-07-11 18:34                 ` Adrien Nader
2016-07-11 20:36                   ` Daniel Bünzli
2016-07-11  9:49             ` Goswin von Brederlow
2016-07-12 18:32           ` Ian Zimmerman
2016-07-12 19:01             ` Gabriel Scherer
2016-07-12 21:26               ` Ian Zimmerman
2016-07-12 22:35                 ` Gabriel Scherer
2016-07-12 23:20                   ` Ian Zimmerman
2016-06-27  9:09 ` Goswin von Brederlow
2016-06-27 11:19   ` Gerd Stolpmann
2016-06-27 13:21     ` Gabriel Scherer
2016-06-30 11:08       ` Goswin von Brederlow
2016-06-30 15:52         ` Gabriel Scherer
2016-06-30 10:59     ` Goswin von Brederlow [this message]

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=20160630105920.GA16808@frosties \
    --to=goswin-v-b@web.de \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).