Adam Fraser

Yes. So far we have had that perspective that it makes sense to define `Associative` instances for these types (see [here](https://github.com/zio/zio-prelude/blob/9bbfa4fd23b85b67f58b71c46ff4f7c85ab243c4/src/main/scala/zio/prelude/Associative.scala#L80)) on the theory that if you are using floating...

I'm not sure if we need to do the by name parameter since we are doing this at compile time but we potentially could. I'm not sure we get that...

I think evaluating something at compile time already kind of tells a different story but I don't think it is a problem to make it by name and looks like...

Hmmm. My experience has been that organizations that use `Validation` also create their own error types when they do need to throw exceptions, though I'm sure practices vary. This seems...

@regiskuckaertz This is definitely a good topic. I think the main issue here is that this signature is not stack safe. I think we could do a version with `ZPure`...

@sideeffffect Blast from the past, right! I spent some time on this yesterday and I think unfortunately it is more complicated. We can definitely implement some kind of stack safe...

I will add.

I wonder if we need a free semiring structure like `Cause` here to capture the potential parallel and sequential structure of the log.

It would definitely allow defining instances for a greater variety of "industrial strength" hashing algorithms. However, it would also move us a bit farther from the Scala standard library. We...

I don't have a particularly strong feeling about this. I think ideally users shouldn't really have to interact with `Id` directly and it should just be used to implement different...