types for serialization variant

[cornerman]

We could have types for marking the different serialization variants in the typesystem.

For json, we could have a tagged String type Json and for boopickle a tagged ByteBuffer Boopickle. This way, it is much more explicit when requiring a Serializer[Json] instead of just a Serializer[String].

[cornerman]

Does it make sense to subsume different json libraries under one type Json? Or should they have distinct types like Circe or Upickle to represent different encoding of e.g. trait hierarchies?

The encoding of trait hierarchies might also be influenced by a configuration in the library.

[cornerman]

I do not want to pull in dependencies like scalaz just for having tagged types. We could e.g. use: https://github.com/Treev-io/tagged-types

[cornerman]

What we want is to have multiple tagged types that give semantic to the used String (for Json) and ByteBuffer or Array[Byte] (for binary serializers).

So we have a tagged type for each library: CirceJson, UPickleJson, BoopickleBytes, ..

Furthermore it would be useful to have library independent types (if it is a protocol) like Protobuf, Json or Boopickle.

We should be aware that some json libraries do not operate on String but on Array[Byte] (example jsoniter-scala). We should be able to adopt this.