hi there! I'm just curious what use-case/problem is solved with the eventually-util::optional::Aggregate trait? I have to admit I got a bit confused digging around the codebase by some of the duplicate object names. I think i've got my head around it now!
It seems to me that this trait is meant to be an analogue of the regular Aggregate trait, but that the state may not be seeded until you receive the first event. Is that about right?
Would it be cleaner to simply add a Default trait bound to the Aggregate::State type?
hi there! I'm just curious what use-case/problem is solved with the
eventually-util::optional::Aggregatetrait? I have to admit I got a bit confused digging around the codebase by some of the duplicate object names. I think i've got my head around it now!It seems to me that this trait is meant to be an analogue of the regular
Aggregatetrait, but that the state may not be seeded until you receive the first event. Is that about right?Would it be cleaner to simply add a
Defaulttrait bound to theAggregate::Statetype?