Andreas Herrmann

> effectively swapping `-optl-static` under `compiler_flags` for `fully_static_link` as an argument to `haskell_binary`, right? Yes, for `features = ["fully_static_link"]` to be precise. > Playing devil's advocate, I do wonder if...

> The packages as structs idea is tempting (and cute), but doesn't that point towards writing the same metadata in a new top-level target instead? That would feel more Bazely....

> Repository rules don't have providers, but they can read files. That's true, but they cannot read files that are generated by build actions because of the different phases in...

Configuring this in `snapshot.yaml` would be great. Unfortunately, we don't have access to flags or GHC options defined in the stack snapshot, `stack ls dependencies json` doesn't expose these.

With custom stack snapshots it's possible to define per package flags and GHC options. The [docs](https://docs.haskellstack.org/en/v1.9.3/custom_snapshot/) give the following examples: ``` # Override flags, can also override flags in the...

> Hm, do we have a feature request upstream? I've opened https://github.com/commercialhaskell/stack/issues/5372 to that end. > As things stand, using a snapshot file is going to be pretty confusing to...

Thank you for raising this! I agree the docs on IDE integration could definitely use improvement. As they say at the beginning, the current status is preliminary. I'd be very...

Thanks for clarifying and explaining the query. > Well, some `from_source` targets are failing because they cannot find some C symbols, which is not happening when using `from_binary`. That's totally...

> However, due to the collective evaluation of module extensions with bzlmod, we could go further and also import transitive Nix dependencies into Bazel in a way that handles overlapping...

> I'm interested to start working on this. @tshaynik Thank you, that would be a valuable contribution. The upcoming Bazel 6 release is targeted to use bzlmod by default, so...