These are chat archives for RBMHTechnology/eventuate

7th
Jun 2017
Volker Stampa
@volkerstampa
Jun 07 2017 07:29
Could you please elaborate a bit on the expected safeness here? If you are concerned about mutability maybe its worth noting that all Seq that are used in eventuate should be scala.collection.immutable.Seq, i.e. they are immutable as opposed to the standard scala.Seq.
Jacob Barber
@Jacoby6000
Jun 07 2017 07:34
No, my concern is that Seq has more than just immutable/mutable counter-parts. The main issue being that Stream inherits from it. If at any point my code is accepting a Seqand then converting to a List or Vector, or running a fold, or doing anything that requires eager evaluation, there's a chance it's going to cause the JVM to hang or throw an OOM.
If I know that the things coming from eventuate could never be a Stream, or something else lazy, then I can insulate the rest of my code from that abstraction.
Volker Stampa
@volkerstampa
Jun 07 2017 09:41
Thanks for clarifying. Indeed eventuate does not make use of scala Streams, so it should be safe to convert Seqs to List or Vector.
Jacob Barber
@Jacoby6000
Jun 07 2017 19:18
What are the types of the Seq's coming back from eventuate, usually?