[erlang-questions] [ANN] Erlang/OTP 18.0-rc1 is available for testing.

[Felix Gallo]

The new time functionality looks excellent, thank you very much!

I feel like erlang:unique_integer/1's doc, as well as the time page where
it's discussed, could use some warnings.  In particular, the invariants are
lost if the value leaves the currently running erlang instance; either by
being included in a message to another instance, or by roundtripping
through any IO path, for example restoring state from a text file or
database after an instance or system crash.  A number of novel edge-casey
production surprises lie in wait for the uncareful implementor.

Does the OTP team have any intention to, or thoughts on, implementing
'distributed' as a possible ModifierList entry for unique_integer/1,
ensuring unique integers with respect to the visible nodes?

F.

On Thu, Mar 26, 2015 at 11:12 AM, Jesper Louis Andersen <
jesper.louis.andersen@REDACTED> wrote:

>
> On Thu, Mar 26, 2015 at 5:32 PM, Kenneth Lundin <kenneth.lundin@REDACTED>
> wrote:
>
>> Erlang/OTP 18.0-rc1 is available for testing.
>
>
> I'm asking this one for the community: what is the status of dirty
> schedulers and release 18.0? Will they be enabled by default, or will they
> still be behind a compiler flag?
>
> Also, the time API is really well-designed. I can't wait to use it. The
> idea of decoupling time and then disabling time smearing but enabling
> monitors for time changes is probably the right way forward. One could
> always imagine having a "smeared time" as well in the future if someone
> really needs the smearing behavior. But one could also argue such things
> should reside in NTP relays/proxies.
>
>
> --
> J.
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150326/b0ca1bb0/attachment.htm>