kuribas / cubicbezier

Haskell library for manipulating cubic bezier curves
BSD 3-Clause "New" or "Revised" License
18 stars 2 forks source link

Build failures with mtl-2.3 #14

Closed sjakobi closed 9 months ago

sjakobi commented 2 years ago
Geom2D/CubicBezier/Overlap.lhs:279:5: error:
    • Variable not in scope:
        replicateM_
          :: Int
             -> SweepStateM ()
             -> StateT SweepState Data.Functor.Identity.Identity a0
    • Perhaps you meant ‘replicate’ (imported from Prelude)
    |
279 | >   replicateM_ nR (yStructDel i)
    |     ^^^^^^^^^^^

Geom2D/CubicBezier/Overlap.lhs:341:40: error:
    • Variable not in scope:
        liftM2
          :: (Ratio Integer -> Ratio Integer -> Ratio Integer)
             -> Maybe (Ratio Integer)
             -> Maybe (Ratio Integer)
             -> Maybe (Ratio Integer)
    • Perhaps you meant one of these:
        ‘lift’ (imported from Control.Monad.State.Strict),
        ‘liftIO’ (imported from Control.Monad.State.Strict)
    |
341 | >         | otherwise = set curveRank (liftM2 between
    |                                        ^^^^^^

Geom2D/CubicBezier/Overlap.lhs:547:5: error:
    Variable not in scope:
      unless
        :: Bool
           -> StateT SweepState Data.Functor.Identity.Identity ()
           -> StateT SweepState Data.Functor.Identity.Identity ()
    |
547 | >   unless (M.null xStr) $ do
    |     ^^^^^^

Geom2D/CubicBezier/Overlap.lhs:843:5: error:
    Variable not in scope:
      when
        :: Bool
           -> StateT SweepState Data.Functor.Identity.Identity ()
           -> StateT SweepState Data.Functor.Identity.Identity ()
    |
843 | >   when (i >= 0 && i < s-1) $
    |     ^^^^

The affected versions on Hackage are v0.4.0.1, v0.4.0.2, v0.5.0.0, v0.6.0.5 and v0.6.0.6.

As a Hackage trustee I have created Hackage revisions for the affected versions that should prevent users from encountering these errors. See e.g. https://hackage.haskell.org/package/cubicbezier-0.6.0.6/revisions/.

ysangkok commented 9 months ago

This was fixed in 0.6.0.7 and the the issue can be closed