Greg Horn
Greg Horn
I can reproduce this as well with a slightly different example: ```haskell {-# LANGUAGE QuasiQuotes #-} module Test ( foo ) where foo :: String foo = [fmt|this causes error|]...
Improving the haddocks https://hackage.haskell.org/package/brittany/docs/Language-Haskell-Brittany.html#t:CLayoutConfig would go a really long way.
You can silence them by supressing all warnings with `-w`, so you have to do `-fallow-argument-mismatch -w`
OK. I have code for generating C++ structs from Haskell data, and I generate C++ code which converts these structs to and from `std::vector` in a way that is compatible...
> Can you give an idea of what your current solution looks like? I have something like toCxxType :: ToCxxType a => Proxy a -> CxxType and generateCxxCode :: [CxxType]...
This was caused by c2hs https://github.com/haskell/c2hs/issues/152
I was going to add a feature request to add HIGHS as as solver, and i found this issue. I noticed that the [HiGHs documentation](https://ergo-code.github.io/HiGHS/dev/interfaces/python/) points to https://pypi.org/project/highspy/, not to...
Thanks for the suggestion. The thing that makes this non-trivial is that the irregular sensor timings make it NOT akin to the OCP one. If you help me figure out...
This is an offline problem, but I don't care if you know the answer :). I do know how to calculate the state and expected sensor functions at an arbitrary...
*I don't care that it is an offline problem if you know the answer. Not "I don't care if you know the answer or not" :p