Sergey Torgashov

@BusyByte , thank you for the report! Would you mind adding an example with `Show` that causes the issue please?

I think it is quite odd that `NonEmptySeq` does have `updated` whereas `NonEmptyList` does not. Apparently, `NonEmptySeq` can wrap `List` under the hood, therefore `updated` may or may not be...

@yisraelU , thank you for the reply! Perhaps, I missed something from docs and source code. So I'd appreciate if you could help me to figure it out. I have...

The primary purpose of `x.some` is to improve type inferrence in certain cases: ```scala import cats.syntax.option.* def fc[A](a0: A, as: A*)(f: A => Boolean)(c: (A, A) => A): Option[A] =...

`x.some` is as safe as `Some(x)` is but provides better type inference in certain scenarios – that's its only purpose. `Option(x)` works too, of course, but contains additional check for...

@johnynek > I have no idea why the NotNull[T] was added, but also we need >: Null I was wondering once too and asked pretty much the same question in...

There is a discussion about the `catchOnly` method itself in #4616. It seems this and similar methods do not exactly meet the Cats convention for methods to be "safe" and...

Arman decided to raise the stakes 😄

Thank you for the bug report! Indeed, it looks like a new Lint warning introduced in Scala v2.13.17: - scala/scala#11033 (initial implementation) - scala/scala#11120 (further refinements) The warning is emitted...

Perhaps, in your case the simplest yet least ivasive way to work-around it is to suppress the warning on the `compose` method of the concern specifically: ```scala implicit val catsInstances:...