Michael Arnaldi

we could even think of something like: ```ts import { Data } from "effect" class User extends Data.Class({ byRef: ["a.b"] }) {} ```

> Could this be an option too? > > ```ts > import { Data } from "effect" > > class User extends Data.Class name: string; > metadata: { foo: string...

Alternative idea: we could use decorators instead of parameters for classes I think we need to approach this in steps: 1) provide a good way of creating deeply compared data...

> I think decorators could be nice, you could use them for both classes and the other apis from what I recall. > > I remember trying to use them...

> RE: `fp-ts-routing`, the codebase is small, making a 1:1 port should not be difficult > > p.s. However, I don't know if it's of interest to the effect org,...

@IMax153 was playing with a zio-parser port

What's the point of `resolve`, can't we simply call `then`? also please don't use Merge Commits, it is safer to rebase the branch

Need to think about this, namely we need to explore better the implications with a potential api extension, currently secret is backed by a byte array and it only accepts...

1) Data stands for Data Type, those are known with different names depending on the language (Data Objects, Value Objects, Case Objects, Immutable Objects) 2) Case is a leftover, it...

They are not part of Effect, the advise is to use Effect directly, for example State can be simulated with: ```ts interface NumberState { readonly _: unique symbol } const...