That convinced me +1. rng or lang both feels good to me.
Regards,
Amey
On Fri, Aug 4, 2017 at 11:40 PM, Gary Gregory <garydgreg...@gmail.com>
wrote:
> For example, I have a enum like:
>
> public enum CardinalDirection (NORTH,SOUTH,EAST,WEST)
>
> and I want to say
>
> traveler.travel(nextRandomDirection());
>
> where
>
> public CardinalDirection nextRandomDirection() {
> return rng.next(CardinalDirection.class);
> }
>
> Gary
>
> On Fri, Aug 4, 2017 at 11:02 AM, Amey Jadiye <ameyjad...@gmail.com> wrote:
>
> > Hi,
> >
> > What's usecase for this BTW ? Might be unaware about requirement but this
> > forced me to think why would someone need random enum ?
> >
> > Enums are generally "limited" immutable constants and people choose enum
> > over the array of constants for good reason, however random provider
> seems
> > best suited for choosing value from any Data-Structure holding "lot" of
> > values.
> >
> > I think it's little weird but I would be happy if someone explain
> > advantages. :-)
> >
> > Regards,
> > Amey
> >
> > On Fri, Aug 4, 2017, 11:17 PM Gary Gregory <garydgreg...@gmail.com>
> wrote:
> >
> > > Hi All,
> > >
> > > Any thoughts on generation when you want to the domain to be an enum?
> > >
> > > SomeEnum e = UniformRandomProvider.next(SomeEnum);
> > >
> > > ?
> > >
> > > Is that too weird for this component?
> > >
> > > Gary
> > >
> >
>
--
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
