2

I have a method exposed on my API that looks like this:

def read[T](implicit decoder: Decoder[T]): T

A user can bring along any T they like and my code will attempt to parse the json result into a T.

The issue I want to resolve is that any user must also import io.circe.generic.auto._ in order to get this to work and auto-derive the Decoder[T].

Is there any way I can change my API to avoid the user having to bring this import?

Stephen Thompson
  • 29
  • 1
  • 6
Cheetah
  • 13,785
  • 31
  • 106
  • 190
  • 1
    Your description isn't quite correct. The user cannot bring any `T`, they can only bring a `T` for which there is an implicit value of type `Decoder[T]`. It is important that the user is aware that this depends on the `circe` library, not your code, so it is good that they are required to have that `import`. – Tim Sep 13 '18 at 09:16
  • Agree with @Tim, but would also like to note, that using `io.circe.generic.auto` may have cause weird side-effects: it generates Decoder[T] every time you try to resolve the implicit in a new scope, so you may end with a separate decoder instance for each method requiring `implicit decoder: Decoder[T]` – shutty Sep 16 '18 at 14:48

1 Answers1

0

It could be if you do it in a library - implicits would easily conflict causing troubles for your users.

In Typelevel Scala 4 can use customizable imports - it didn't landed in Scala 2.12 but (after several iterations) landed on 2.13. You could recommend your users have some implicits always in scope this way once 2.13.0 is released, but that will be conscious decision on their part.

Mateusz Kubuszok
  • 24,995
  • 4
  • 42
  • 64
  • Hmm - your code doesn't appear to work (it doesn't compile). I did try exploring your idea of using a type alias, but I didn't come to anything. Yes this is for a common module/library shared between the application. – Cheetah Sep 15 '18 at 12:54
  • I guess you put type alias directly in the file, which Scala doesn't allow. Put it into package object and try to compile again. – Mateusz Kubuszok Sep 17 '18 at 07:46
  • Type alias was in a package object, the code you posted doesn't compile (nothing to do with the type alias, its the implicit that is defined) – Cheetah Sep 17 '18 at 08:07
  • I could have sworn it worked and I used it in my code, but apparently I was wrong. I edited the answer. – Mateusz Kubuszok Sep 17 '18 at 08:56