colll78

https://github.com/cardano-foundation/CIPs/pull/749 https://github.com/cardano-foundation/CIPs/pull/735 I would also like to introduce: 1. `txInfoObservations :: [ScriptHash] ` as a field to the `TxInfo` in the `ScriptContext` 2. Add new `Maybe BuiltinData` field to `TxOut`...

I agree with the @KtorZ @micahkendall's points above; however, I would add that: > So some functions (e.g. inserting & union) can be made faster -- though they are often...

+1 for making this an empty value. Right now, the behavior is completely unintuitive, and introduces a ton of issues in development. You would expect to be able to check...

With a correct equality function this should return false, because it is not actually the case the the value is empty. You can do this if you have a weird...

From my perspective, this is a very big deal. Using a let while folding on inputs / outputs is very common. 10% is very significant (and tests that I have...

> can be very far from its LHS and the whole thing is generally quite unreadable, especially when some of the application are iterated (check it out yourself by reading...

``` instance PlutusTx.Eq.Eq ScriptPurpose where (==) a b = PlutusTx.toBuiltinData a == PlutusTx.toBuiltinData b ```

I wrote an entire CIP about this: https://github.com/cardano-foundation/CIPs/pull/767 Please consider raising the priority of this issue. It is an extremely large pain point for production smart contract development throughout the...

> Additionally, I would like to have functions for lazy access of script context from plutus so that I don't have to remember the inices of fields. I have written...

https://github.com/cardano-foundation/CIPs/pull/749 https://github.com/cardano-foundation/CIPs/pull/735 I would also like to introduce: 1. `txInfoObservations :: [ScriptHash] ` as a field to the `TxInfo` in the `ScriptContext` 2. Add new `Maybe BuiltinData` field to `TxOut`...