Daniel Esik

Good idea, @benhutchison! I've left a comment about Scala 3 migration in your PR, but I will repeat my thoughts here too. I propose to have one `main` branch and...

Thank you for your contribution! I like those methods, and having them is reasonable to me. I just wonder if we can have it in the collections library straightforwardly to...

I rather meant allocations when using the `list.tailOrEmpty` syntax method (allocation for `ListOps` instance to be precise).

According to my little [investigation](https://github.com/scala/scala-library-next/issues/127), we can't add new API methods to the std library for Scala 2 due to compatibility constraints. Also, we can't do it for Scala 3...

> `tailOption` to mean non-empty tail That's interesting. I'd suggest this would be even more intuitive from a contract point of view.

This is a kinda controversial topic :) I mean, I was always getting stuck when faced `Option[List[A]]`: is `Some(Nil)` equal to `None`? But yeah, if we wanna be a literalist,...

It'd be cool if we have managed to call more people to get their thoughts on this topic. Because I'm 100% biased here. > "boy, I wish this was what...

If @TobiasRoland doesn't mind, I can help with moving this PR further.

So, I've tweaked some things: 1. `tailOption` returns `Option[NonEmptyList[A]]` and `Option[NonEmptySet[A]]` accordingly now 2. all of these new syntaxes are available for Scalajs on Scala 3 It isn't strict and...

@benhutchison I had to add a constructor for the creation of `SortedSet` due to changes in the API of the collections library in 2.13. The previous API of the creation...