Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why isn't ByteString converted automatically to FilePath?

I'm passing a (strict) ByteString to something expecting a System.IO.FilePath, which is declared as type FilePath = String. I'm also using {-# LANGUAGE OverloadedStrings #-}. I've had conversions in some places happen automatically, but here it does not. What have I got wrong?

Main.hs:33:40: error:
    • Couldn't match type ‘ByteString’ with ‘[Char]’
      Expected type: FilePath
        Actual type: ByteString
like image 299
Matt Joiner Avatar asked Dec 02 '22 11:12

Matt Joiner


2 Answers

The {-# LANGUAGE OverloadedStrings #-} pragma only works for string literals, like "a string". In that case, Haskell implicitly places a fromString before every string literal, so it rewrites a string literal as "a string" to fromString "a string". This only happens for literals.

In Haskell, as far as I know, there are no implicit conversions. Conversions between for instance Int and Float are all explicit.

Furthermore note that the IsString typeclass only has a function fromString :: String -> a. So that means it works only from a string to that instance (here ByteString), not the other way around.

You can use the unpack :: ByteString -> String to convert the ByteString to a String.

like image 191
Willem Van Onsem Avatar answered Dec 15 '22 00:12

Willem Van Onsem


IIRC, the OverloadedStrings extension doesn't enable magical conversion between different types of data. What it does is that when you write a string literal like "foo", the compiler can treat that literal as not only a String, but also as a ByteString.

You probably need something like unpack to convert ByteString to String.

like image 35
Mark Seemann Avatar answered Dec 14 '22 23:12

Mark Seemann