-
-
Notifications
You must be signed in to change notification settings - Fork 28
Open
Description
Hello,
I am trying to compile Pandoc at an older commit and it fails due to the compilation of tasty-lua.
I receive the following error:
[1 of 5] Compiling Test.Tasty.Lua.Arbitrary
src/Test/Tasty/Lua/Arbitrary.hs:65:43: error:
• Could not deduce (Read HsLua.Core.Integer)
arising from a use of ‘peekIntegral’
from the context: LuaError e
bound by the type signature for:
registerDefaultGenerators :: forall e. LuaError e => LuaE e ()
at src/Test/Tasty/Lua/Arbitrary.hs:62:1-52
There are instances for similar types:
instance Read Prelude.Integer -- Defined in ‘GHC.Read’
• In the third argument of ‘registerArbitrary’, namely
‘peekIntegral’
In a stmt of a 'do' block:
registerArbitrary "integer" pushinteger peekIntegral
In the expression:
do registerArbitrary "boolean" pushboolean peekBool
registerArbitrary "integer" pushinteger peekIntegral
registerArbitrary "number" pushnumber peekRealFloat
registerArbitrary "string" pushString peekString
|
65 | registerArbitrary "integer" pushinteger peekIntegral
| ^^^^^^^^^^^^
src/Test/Tasty/Lua/Arbitrary.hs:66:43: error:
• Could not deduce (Read Number)
arising from a use of ‘peekRealFloat’
from the context: LuaError e
bound by the type signature for:
registerDefaultGenerators :: forall e. LuaError e => LuaE e ()
at src/Test/Tasty/Lua/Arbitrary.hs:62:1-52
• In the third argument of ‘registerArbitrary’, namely
‘peekRealFloat’
In a stmt of a 'do' block:
registerArbitrary "number" pushnumber peekRealFloat
In the expression:
do registerArbitrary "boolean" pushboolean peekBool
registerArbitrary "integer" pushinteger peekIntegral
registerArbitrary "number" pushnumber peekRealFloat
registerArbitrary "string" pushString peekString
|
66 | registerArbitrary "number" pushnumber peekRealFloat
| ^^^^^^^^^^^^^
Error: cabal: Failed to build tasty-lua-1.0.2 (which is required by
test:test-pandoc from pandoc-2.17.0.1). See the build log above for details.
The relevant versions are
tasty-lua-1.0.2
cabal 3.10.1.0
ghc 8.10.7
Does this seem like a fixable thing? Or do I have to abandon this ship
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels