Alexey Kuleshevich

Ok, we might have a solution for this, which would require minimal amount of work. The most important part of the solution is for `mkEvaluationContext` to never fail if it...

> I believe both are phase-1 failures, not phase-2. Yes, that will be either `MalformedScriptWitnesses` or `MalformedReferenceScripts` phase 1 validation failure, depending on where in the transaction the script is....

I think we should stick to the manual approach. It has proven to work great so far and I don't think we want this automation anyways, since our changelogs are...

There is already `readMaybe`. So, I'd vote for consistency and use `Maybe` as a suffix, rather than the prefix: `indexMaybe` Despite that with the prefix it reads better in English....

@Shimuuar My vote is: * +1 for 1 - Consistency with base and other really popular libraries like `rio` is very valuable. * 0 for 2 - Shortness of `May`...

> So there's an unanimous support for the Maybe suffix. Which we should use I love it! It took us only 4 short messages to decide on the naming scheme....

This is only really applicable for generating some basic types in the full range, because in many cases without forcing the new value you cannot get the new generator. I...

> I don't understand the first paragraph, sorry. Can you explain more? Certainly. For example you want to generate an `Int` in the range `[0,10]`. In order to avoid bias...

Could you elaborate on that: > leave generation of Complex numbers using dedicated function. Also. I don't agree that this is a good reasoning: "There are multiple ways to do...

> I think it's perfectly valid reasoning. If that was the case there would be no `Random Float` and `Random Double` instance. Do we select `[0, 1)`, `(1, 0]` or...