Georgi Krastev
Georgi Krastev
Although it probably wouldn't be too hard to read the annotation from the type only when we need to produce an error.
I think I would prefer deriving as much as possible. If I have some nested ADT and I only care about having a codec for the top-level type, why should...
I guess we could just add another method to do this in Magnolia, but how would we call it?
Should be careful with inlining because you don't want to produce too big trees 😄 But it could be a feature for expert users.
One example is `Default` for a sealed trait: ```scala sealed trait MaybeDate case class ADate(date: Date) extends MaybeDate case object NoDate extends MaybeDate ``` If I don't have a default...
Most likely the problem is that there are many `b`s - the (private) field `b`, the getter method `b`, the constructor parameter `b` and the `apply` method parameter `b`. The...
It may be possible. I don't know if it's desirable. Check how `Deferred` is used. In a similar fashion you could use a `Failed` dummy to collect all errors and...
The approach outlined above might also simplify the error handling logic in the stack.
Whenever we need to have a recursive reference to a `lazy val` we put a `Deferred("name of the val")` instead and there is a final stage that replaces each `Deferred`...
We can't use `Validated`. We can only do two things in a macro: 1. Abort immediately on the first error 2. Return a valid AST that typechecks It might seem...