Joshua Chia

The exports executable in the cabal still requires base

> Is `--depth=1` what @fgaz called a "shallow clone" above? Does the workaround work for you? What is `--depth=1`? A cabal build option? I don't see it in the help....

Nothing complicated or surprising. The hs-source-dirs is not picked up from the common stanza. ``` cabal-version: 2.2 name: test version: 0.1.0.0 description: test category: test build-type: Simple common common default-language:...

Having a range-checking parser for bounded integral types means that excessively-long input can be rejected early before running out of memory from trying to parse an Integer or Natural. This...

@peti Which version of gcc are you using? Are you using a version older than 7? In such cases, the `typedef` line is compiled: ``` # if !__GNUC_PREREQ (7, 0)...

@peti I suspect that under GCC 7 the problem goes away, as elucidated in https://github.com/visq/language-c/issues/43. Would it be easy for you to try GCC 7 and test my theory?

@peti I think this issue depends on [this language-c issue](https://github.com/visq/language-c/issues/43). If that issue is solved, this issue is solved.

I meant `insMapNode`, not `mkNode`.

I'm using gcc 7.2.0 and getting an error that also mentions 128-bit floating point: ``` c2hs: C header contains errors: /usr/include/stdlib.h:133: (column 18) [ERROR] >>> Syntax error ! The symbol...

I think the error I saw is a result of `_Float128` being unrecognized by `language-c` when it tries to process a line like this from `stdlib.h`: ``` extern _Float128 strtof128...