Client API feels inconsistent

There are four expect methods:

def expect[A](s: String)(implicit d: EntityDecoder[F, A]): F[A]
def expect[A](uri: Uri)(implicit d: EntityDecoder[F, A]): F[A]
def expect[A](req: F[Request[F]])(implicit d: EntityDecoder[F, A]): F[A]
def expect[A](req: Request[F])(implicit d: EntityDecoder[F, A]): F[A]

1. The first two work like special cases where the request is a GET. At the same time, there are two methods called get with the exact same parameters as the first two expects. The same is happening for the expectOr methods.

2. There is the method:

   def expectOption[A](req: Request[F])(implicit d: EntityDecoder[F, A]): F[Option[A]]
   

   But there isn’t the corresponding one for F[Request[F]]:

   def expectOption[A](req: F[Request[F]])(implicit d: EntityDecoder[F, A]): F[Option[A]]
   

3. Tha API has a dedicated DSL for GET requests but not for other commonly used methods: DELETE, PUT, POST, HEAD.

[ChristopherDavenport]

Remove/Deprecate all overloads.

[kevinmeredith]

Would it be worthwhile to deprecate/remove def expect[A](s: String)(implicit d: EntityDecoder[F, A]): F[A], i.e. require a valid Uri to be passed rather than a String?

Uri > String motivates this question.