Sergey Torgashov

@rossabaker , thank you for the review! > I'm sorry it got so desperately lonely you had to talk to a bot. No worries! Actually, I just wanted to check...

A question... Should the rule only emit warnings and suggest users do the renames themselves or do the renames on behalf of the users? As I can see, the `MapSequence`...

I think we can arrange something in the middle. For example: 1. Add the aliases but do not deprecate the old method names. 2. When cutting the next release, mention...

Agree, a scalafix rule could come in handy indeed. I would suggest though to address it in a separate follow-up PR, i.e.: 1. Introduce aliases; 2. Create the scalafix rule...

Thank you @LukaJCB ! I didn't realize that there was another discussion when I created this one. (In fact, in 2017 I was not involved into the Typelevel community yet...

Perhaps, [mouse](https://github.com/typelevel/mouse) can help out with that `F[Option[...]]` case: ```scala import mouse.foption.* def lookupSomething(id: ID): F[Option[Something]] = ??? val res: F[Something] = lookupSomething(id).getOrElseF { log(s"nothing found for $id") >> F.raiseError(new...

Closed by #4711, thanks!

Ah, sorry, I overworked it a little. In Cats it is a generic `A`, not `Int`: https://github.com/typelevel/cats/blob/90db3cd0269cf2b621ad6460ded594aee2e6a135/kernel/src/main/scala/cats/kernel/Enumerable.scala#L25-L34

@armanbilge could you provide a clue why v1.15.0 is so concerning please? Perhaps I missed something – have no idea now.

yeah, I see now. Thanks for the clarification. Perhaps (imo), since it is on Maven Central anyway it would probably better to restore the deleted tag back.