feat(Vm): function or any Value that can be store in a env · AxelHumeau/LobsterLang@131b2b1

Run tests: LobsterLang/test/ParseSpec.hs#L20

• Couldn't match type: [Char]

Run tests: LobsterLang/test/ParseSpec.hs#L20

• Couldn't match expected type: String

Run tests: LobsterLang/test/ParseSpec.hs#L22

• Couldn't match type: [Char]

Run tests: LobsterLang/test/ParseSpec.hs#L22

• Couldn't match expected type: String

Run tests: LobsterLang/test/ParseSpec.hs#L24

• Couldn't match type: [Char]

Run tests: LobsterLang/test/ParseSpec.hs#L24

• Couldn't match expected type: String

Run tests: LobsterLang/test/ParseSpec.hs#L26

• Couldn't match type: [Char]

Run tests: LobsterLang/test/ParseSpec.hs#L26

• Couldn't match expected type: String

Run tests: LobsterLang/test/ParseSpec.hs#L28

• Couldn't match type: [Char]

Run tests: LobsterLang/test/ParseSpec.hs#L28

• Couldn't match expected type: String

Run tests: LobsterLang/src/Parse.hs#L43

The import of ‘GHC.IO.SubSystem’ is redundant

Run tests: LobsterLang/src/Parse.hs#L45

Defined but not used: type constructor or class ‘Col’

Run tests: LobsterLang/src/Parse.hs#L46

Defined but not used: type constructor or class ‘Row’

Run tests: LobsterLang/src/Parse.hs#L66

• No explicit implementation for

Run tests: LobsterLang/test/AstEvalSpec.hs#L1

The export item ‘module AstEvalSpec’ is missing an export list

Provide feedback