nibbles: failed to compile hs (zip by scalar)

[whio]

Nibbles code:

! ,4 0 ~ 1

Produces the following error message:

out.hs:192:824: error:
    • Couldn't match type ‘Integer’ with ‘[t0]’
      Expected type: [Integer] -> Integer -> [Integer]
        Actual type: [Integer] -> [t0] -> [Integer]
    • In the third argument of ‘\ a b f -> f a b’, namely
        ‘(((zipWith . \ f a b -> f $ (\ (~a1, ~a2) -> ((a1, a2))) (a, b))
             (\ (arg2t1, arg2t2)
                -> (((((id) (((1)) :: Integer))) :: Integer)))))’
      In the first argument of ‘id
                                . ((\ a b -> intercalate a $ map (sToA . show . confirmInt) b)
                                     secondSep)’, namely
        ‘((((\ a b f -> f a b)
              ((((\ x -> [1 .. x]) ((((id) (((4)) :: Integer))) :: Integer))) ::
                 [Integer]))
             (((\ f -> f (()))
                 (\ (arg2t1) -> (((((id) (((0)) :: Integer))) :: Integer))))))
            (((zipWith . \ f a b -> f $ (\ (~a1, ~a2) -> ((a1, a2))) (a, b))
                (\ (arg2t1, arg2t2)
                   -> (((((id) (((1)) :: Integer))) :: Integer))))))’
      In the expression:
        ((id
          . ((\ a b -> intercalate a $ map (sToA . show . confirmInt) b)
               secondSep))
           ((((\ a b f -> f a b)
                ((((\ x -> [1 .. x]) ((((id) (((4)) :: Integer))) :: Integer))) ::
                   [Integer]))
               (((\ f -> f (()))
                   (\ (arg2t1) -> (((((id) (((0)) :: Integer))) :: Integer))))))
              (((zipWith . \ f a b -> f $ (\ (~a1, ~a2) -> ((a1, a2))) (a, b))
                  (\ (arg2t1, arg2t2)
                     -> (((((id) (((1)) :: Integer))) :: Integer)))))))
nibbles: failed to compile hs (likely an internal nibbles bug, please report it!)
CallStack (from HasCallStack):
  error, called at nibbles.hs:163:24 in main:Main

[darrenks]

This is indeed a bug, but there is never a reason to do a generic zip with a scalar right? You could do a map (and a save if needed) in the same length. Ideally this would be handled or a proper error message, but I probably won't get to it.