Sergey Torgashov

@mrjonjonjon yes, looks like so... But seems there's no clear and ready-to-use solution yet.

Hi guys. Just curious – any progress on this issue? I also faced this issue in my project some time ago and came up with a similar solution eventually. But...

Agree. I am kind of 👍 for getting rid of over-use of `apply` methods in favor of explicitly named static ones.

I think it's in the accordance with the RFC: https://datatracker.ietf.org/doc/html/rfc3986#section-3

Just a side note: Refined still has an advantage in some cases because it provides a macro-based compile-time literal parsing. Which can be somewhat cool.

@armanbilge, fyi: ``` warning: tutorial.md:236:9: a type was inferred to be `Any`; this may indicate a programming error. (IO(in.close()), IO(out.close())) ^ ``` https://github.com/typelevel/cats-effect/blob/e116186a3d008be12f9e814ce77f491e469352f7/docs/tutorial.md?plain=1#L235-L238 can be fixed by moving `.void` before...

Looks similar to this one: #278 But seems there's still no direct solution yet.

Hi guys. Just wondering – any activity on this PR? Seems this functionality is a really nice-to-have one.

@mdedetrich but is it really necessary to extend `Gen` for that? There's a _public_ method `infiniteLazyList` (or `infitineStream`) in `Gen` that (I think) can be used to achieve pretty much...

@lambdani just to clarify: is the suggested behavior different from this one? ```scala def shuffledPick[T](n: Int, seq: IndexedSeq[T]): Gen[collection.Seq[T]] = { Arbitrary.arbitrary[Long].flatMap { seed => val shuffledSeq = new scala.util.Random(seed).shuffle(seq)...