dmjio
dmjio
yea, it just uses the `Read` instance for `Bool`. ```haskell instance Var Bool where toVar = show; fromVar = readMaybe ```
You can make your own though. ```haskell newtype Thing = Thing Bool instance FromEnv Thing where fromEnv _ = fmap Thing $ (True
Also note for decoding basic type the failure information returned isn't that useful, so this change might not be worth it. ``` >>> readEither "hello" :: Either String Int Left...
@cideM we can change `fromVar` to be `fromVar :: String -> Either String a`. I'd support that change.
I've contemplated making an `Either EnvError a` type, defined as: ```haskell type FieldName = String data EnvError = NotFound String | ParseError FieldName String ``` This would mean making `fromVar`...
@StevenXL tldr; yes, something like should be added to the library imo. Modifying `envMaybe` to call `env` is the right approach imo.
@TheMaverickProgrammer, thanks, I ended up just going with `alex` and `happy` since I can lex directly into a `Bool`.
@NickSeagull, @mdibaiee, extremely excited about this effort, would love to be of help in any way.
@valderman @jurriaanhage, yes it will be interesting to see what kind of type errors occur if/when we approach type level `Query`. I can say that the early type-level table (table-families?)...
@valderman, @jurriaanhage continuing the conversation... :) Experiments have shown `CREATE` / `DROP` `TABLE` do well. From the type-level representation above, we can reify into a `Builder` and efficiently construct a...