Re: [Caml-list] concurrent gc?

[Gabriel Scherer <gabriel.scherer@gmail.com>]

This is not a bug, at best a feature request (of the kind "we've
already talked about plenty of times and nobody stepped forward to do
actual work to demonstrate usefulness"). You can optimize your data
representation this or that way, and they will work better or this or
that workflow.

Do you have practical experience with OCaml programs with unacceptable
pauses, or is this discussion just premature GC optimization? Having a
concrete example to work with could be interesting.

On Mon, Jul 28, 2014 at 7:34 PM, Raoul Duke <raould@gmail.com> wrote:
>>> There are also other tricks such as changing the tag of a block to avoid
>>> scanning, but I wouldn't advise to use it unless you really know what you
>>> are doing...
>> That is actualy something that should be fixed in the compiler. There
>> are some special cases that use special tags, e.g. a record only
>> containing floats will be tagges as float array. But any record that
>> contains no pointers should be tagged so it isn't needlessly scanned.
>> Afaik that doesn't happen yet.
>
> anybody who understands those words willing to open a bug report on it? ;-)
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs