Open bladyjoker opened 4 months ago
The core problem is that lbr-plutus:LambdaBuffers.Runtime.Plutus
import is missing where the missing instance is defined. Why is it missing?
Because during codegen, 'nothing' that requires this import was 'used'.
It's a known problem that we don't specify in our configuration a a mapping from a LB instance
clause and the target module where it's implemented.
> • No instance for ‘PlutusTx.Eq.Eq LambdaBuffers.Prelude.Bytes’
> arising from a use of ‘PlutusTx.Eq.==’
> • In the expression: (PlutusTx.Eq.==) (x2) (x3)
> In the expression: let Script x3 = x1 in (PlutusTx.Eq.==) (x2) (x3)
> In the expression:
> let Script x2 = x0 in
> let Script x3 = x1 in (PlutusTx.Eq.==) (x2) (x3)
> |
> 44 | (==) = (\x0 -> (\x1 -> let Script x2 = x0 in let Script x3 = x1 in (PlutusTx.Eq.==) (x2) (x3) ) )
> | ^^^^^^^^^^^^^^^^
This is getting annoying
Probably a duplicate of #124
To expand on this, as this is utterly my doing. Honestly, it wasn't really clear to me how to separate all this, but now the user aspect has clarified for me and I see things differently.
I'll talk about Haskell related back-ends, which I'll call native Haskell, Plutarch and PlutusTx.
And we have 2 LBF packages, namely Prelude and Plutus!
We have two Nix functions to build lbf schemas for Haskell
Nothing controversial here, this maps to native Haskell which is base and containers library and all opaque types and their instances ofc supported.
This is the codegen config https://github.com/mlabs-haskell/lambda-buffers/blob/main/lambda-buffers-codegen/data/haskell-prelude-base.json
Simple enough.
However, this is shit!!!
I collated two things that shouldn't have been collated:
And now I have this shit
Treat PlutusTx as a separate language.
lbfPlutusTx
codegenes PlutusTx code with configurations plutustx-prelude.json
and plutustx-plutus.json
, since there's some LBF Prelude types that are naturally available in PlutusTx.
The modules generated go into LB.SomeModule.PlutusTx
(similar to how Plutarch backend has LB.SomeModule.Plutarch
)
Have lbfHaskellPlutus
map into native Haskell and not PlutusTx. It should generate code into LB.SomeModule
and use pretty much native Haskell types. This can be used for transaction building for example, and the only dependency is PLA.
Once everything is put together, everything should compile, the fact that it doesn't means this is a bug.
Some deets:
Imports printed
Cabal printed
Workaround
Add this to your problematic schema which will bring in the necessary imports.