effectfully

> Therefore we need to think of a way to ensure things (or at least some subset of them) do not get broken unintentionally. @michaelpj do you happen to know...

@michaelpj > Nothing so far. We'd want to say something like "given the 'same' ScriptContext in V1 and V2, the Data representation is the same", over a wide variety of...

@michaelpj sorry, this wasn't ready for review, I was going to add more sections, which I now did, please check them out. > So apart from breaking the type system,...

> I didn't mean we can do it automatically, I meant that the user can do it manually. I.e. if am writing some code that uses `constrTermFromConstrData` and I want...

Thanks @zeme-wana! > Please follow [this guide](https://github.com/input-output-hk/iogx/blob/main/doc/nix-setup-guide.md) and try again. Given this, I'm going to triage this issue as "needs info from the reporter".

> Right, so it will always produce a `CekValue.Constr` or fail, but a `CekValue.Constr` is not valid in many places! Right, thanks. We could handle that by hardcoding a typing...

I'm closing the issue given that there's been no info from the reported for more than three months. Do feel free to reopen.

Somebody from the Aiken team (I forgot who it was, sorry) suggested that we could produce a SOP with each of its constructors containing a list of `Data`s, so that...

> I'm a bit confused about what this would entail for the PLC language. > Would there be a new builtin-function? would case be a new language construct? No new...

> What would be the type of `caseList`? It's in the PR, the `plutus-core/plutus-core/test/TypeSynthesis/Golden/CaseList.plc.golden` file (there's a golden file with a type signature for every builtin, including the proposed ones):...