Re: [DISCUSSION] rename StateSpecs.combiningValue?

2017-04-03 Thread Etienne Chauchot
+1 Etienne Le 30/03/2017 à 20:48, Kenneth Knowles a écrit : +1 for a different reason (also: now is the time to revisit names and other bits of the State API before it is too late :-) Folks may not have this catalog in their head. The classes / methods are: ValueState / value(...) BagState

Re: [DISCUSSION] rename StateSpecs.combiningValue?

2017-03-30 Thread Kenneth Knowles
+1 for a different reason (also: now is the time to revisit names and other bits of the State API before it is too late :-) Folks may not have this catalog in their head. The classes / methods are: ValueState / value(...) BagState / bag(...) SetState / set(...) MapState / map(...)

Re: [DISCUSSION] rename StateSpecs.combiningValue?

2017-03-30 Thread Jean-Baptiste Onofré
+0 as the StateSpec takes AccumularCombiningState, it's already "specify" indirectly. Regards JB On 03/30/2017 04:46 PM, Etienne Chauchot wrote: Hi all, Just a 10 cents comment, but maybe a rename of public method nevertheless... There are AccumulatorCombiningState and CombiningState

[DISCUSSION] rename StateSpecs.combiningValue?

2017-03-30 Thread Etienne Chauchot
Hi all, Just a 10 cents comment, but maybe a rename of public method nevertheless... There are AccumulatorCombiningState and CombiningState interfaces, the first extends the second The factory method StateSpecs.combiningValue returns a StateSpec