Arseniy Zhizhelev
Arseniy Zhizhelev
Two ways to achieve this: 1. contact as object (singleton types). ``` val input ``` => ``` object input extends Contact ``` 2. tags ``` sealed trait Input val input...
We may want to first associate individual types with input/output contacts and then attempt to represent them as `HList` of inputs + `HList` of outputs.
There are many places of low quality code. `.sbt`, comments, deprecated features. We might want to fix those issues so that we have clean build.
Current implementation of [`toSet`](https://github.com/zio/zio/blob/series/2.x/core/shared/src/main/scala/zio/FiberId.scala#L75): ```scala final def toSet: Set[FiberId.Runtime] = self match { case None => Set.empty[FiberId.Runtime] case id @ Runtime(_, _, _) => Set(id) case Composite(l, r) => l.toSet...
We might implement Selectable with Fields to make `ValueWithSchema` work like a simple object.
Column itself might have - a function that takes row and returns result - an expression that could be transformed to such function - pseudo-Scala code that is transformed by...
It seems that we could represent values annotated with schema in a really generic way. Currently we have slightly varying representation for single column values and records. We might be...
Case classes in Scala 3 have Mirrors and there is an isomorphism to tuples. We could support arbitrary values that are isomorphic to tuples in all schema operations.
Try to express Transformer as a Profunction (functor + cofunctor).
We have Getter that is separate from transformer. It seems that it could be expressed via more general Transformer.