i did some digging to see if theres a simple fix ... but then i realized
that the current design they have for inlineR always assumes theres IO
available in pure computations ... which they use the s parameter to thread
into the pure vector code via reflection tricks
so it looks like the "right" w
To be clear : I’m annoyed with myself that this impacted a package that
depends on vector, but this does seem to be the case that the newest bug
fix release for vector actually revealed a broken design for the vector
instances / data types in the inline-r package.
To;dr — I suggest patching inline
so i took a look .. (also the inline-r devs seem to have done a hackage
revision so you wont hit that issue in your current setup if you do a cabal
update ..)
and it seems like the type definitions in inline-r are kinda bogus and you
should get them patched ...
the MVector type class, and related
were you using the same version of vector in both setups?
in the most recent vector release we made mutable type family injective
in the vector package for ghc's that support it ...
On Sat, Dec 29, 2018 at 1:50 PM Dominick Samperi
wrote:
> When I use v8.6.3 of GHC under Ubuntu to install the
When I use v8.6.3 of GHC under Ubuntu to install the inline-r package
I get the error "Type family equation violates injectivity annotation," and
a type variable on the LHS cannot be inferred from the RHS, due to
the lack of injectivity (I suppose).
On the other hand, v8.0.2 of GHC (shipped with H
