Michael Arnaldi

> The empty message was intentional, as all the information is in the annotations. Was it breaking something for you? Any reason why a log message would be bad?

> > No not necessarily, the function will return something different and expect potentially different arguments. It's not safe to assume andThen behaviour > > How does such a case...

After a good amount of thinking it I think it is safe to discriminate between `Function` and `NotFunction` so this looks like it is working. The only troubles I can...

Are we logging purely annotations?

I feel like regional would be far too verbose and it's not a solution for classes as you can't creste a class inside the region

@tim-smart I think we need to make a choice here, either we add the param to the api or we decide it's not important. WDYT? cc @IMax153 @gcanti @fubhy

```ts import { Data } from "effect" class User extends Data.Class({deep: true}) {} ``` I don't see any single reason not to add parameters. Constructors don't exist for plain objects...

> Both seem a bit awkward tbh. Also, apologies in advance as I'm probably missing something here, but why would you ever want to use the `Data.proxy()` and then set...

We can make it default if we have an opt-out. Considering everything by value is a mistake, one could have mutable objects and objects with circular dependencies. We once tried...

Note: the issue is not unexpected behaviour, it's absolutely expected not to have deep comparison if you use mutable data such as nested objects. But that doesn't mean the user...