David Kraeutmann

Consider the following project: hsc-bug.cabal ``` name: hsc-bug version: 0.1.0.0 build-type: Simple cabal-version: >=1.10 library exposed-modules: Bug, Bug.Internal build-depends: base >=4.8 && IO CSize ``` `ghc-mod browse Bug.Internal` prints ```...

I understand the appeal, but it feels like extra noise on the schematic + it messes with SPICE setup. Is there something I'm missing in this design decision?

More info about GCD delay distribution (e.g. a histogram)

1

It'd be nice to have a histogram + statistical data on the GCD delay instead of just an estimate. Useful for determining impact of weaves and finding other weird issues.

c2hs is occasionally, but not always segfaulting on our project https://github.com/SimulaVR/Simula (specifically simula-wayland) with stg_ap_p_ret. Haven't tried minimizing the example yet, and it's staggeringly elusive.

GIven a package hierarchy with two packages `a` and `b` and files ``` a/src/Foo.chs b/src/Bar.chs ``` using `{# import Foo #}` in `Bar` fails. Testcase: https://github.com/KaneTW/c2hs-testcase

Feature request: Download all

2

Would it be possible to add an option to download all artists?

Function code response error handling needs improvement

3

Not all function responses can currently be handled. For example, I have a device that outputs FC code 0x2 (RR, resource error) after two weeks of operation. Pyprofibus doesn't notice...

Acyclic communcation support

1

Some devices (MT M700 in this case) require acyclic communication for functionality. It'd be nice to get it implemented.

Provide access to rel8 internals

1

Some applications (e.g. verifying whether a type correctly maps to a schema) require access to rel8 internals. Exposing internal modules would be helpful for that.