-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Here are a lot of instances: https://github.com/ekmett/abelian/blob/master/src/Control/Commutative.hs
Does anyone else try to test executables directly using Haskell. I know the suggested pattern is (don't do that) put your executable code in a library and test that instead. I can't really be bothered to do that to date, even if it is the Right Thing To Do - also a library and executable are not identical, but okay. The problem is without a library it is quite hard to "find" one's built executable in a canonical way: maybe some test library has abstracted this already? I mean that cabal v1 & v2, and stack all build the executable in different places, so for now I just gave up and run my tests with the installed executable: eg this test.hs.
Is there any way to treat 'local packages' as 'external packages'(as in local-versus-external-packages)? My primary question is: After editing a small portion of code from hackage to make it compatible with recent GHC, can I use that package to compile other packages from hackage? I managed to compile and install --lib by making cabal.project suggested here but it was non-trivial job and looks like compiling same packages several times. cat ~/.ghc/x86_64-linux-8.10.4/environments/default shows 'external packages' as text-1.2.4.1 while showing 'local packages' as reflex-0.8.0.0-16cad92f....