Andreas Herrmann

@avdv Thanks for giving this its dedicated ticket! Yes, that's what I had in mind. > Should we try to combine these if both, the attribute and the json file...

@jonathanlking I just saw your [ZuriHac project](https://github.com/zfoh/zfoh.ch/pull/182) "Building statically linked Haskell binaries with Bazel". Very cool! I thought I'd ping you here in case there is added context on this...

Some of the progress from ZuriHac 2023: to update static-haskell-nix and include an appropriate GHC https://github.com/nh2/static-haskell-nix/pull/116 and to test fully static builds on Skyscope https://github.com/tweag/skyscope/pull/94

There is a similar feature request open on rules_rust: https://github.com/bazelbuild/rules_rust/issues/458 Sharing for reference as it may be interesting to see what approach rules_rust takes. Thanks @k1nkreet for the pointer!

@andrevidela the capability repository contains some examples using the reflection module [here](https://github.com/tweag/capability/blob/master/examples/Reflection.hs). These might help to better understand the approach.

I also fear that this is a bit too magical. On the pro side - it does reduce noise and boilerplate a bit, - `foo = use_extension` is different from...

> We still have most repos with `extensions.bzl` which was the common convention for a year or so - and since they don't plan to grow more extensions it will...

We have now successfully applied these changes on a Haskell project to achieve cross package module granular incremental builds. The dynamic value introduced here works to propagate module dependency graphs...

Hi @stepancheg, thank you for taking this on! Yes, of course, no problem if this waits two weeks. :slightly_smiling_face:

@stepancheg I hope you had a good conference and vacation! Did you have a chance to take a look at this since you're back?