John Ericson

Use the rust-specific config when available

1

Per the TODO, we could leverage Nixpkgs to do this better still, but it isn't terribly convenient at this time. I rather do it after the other cross PRs are...

Now that we support cross compilation, it's wrong to have a global `target`. Instead, we keep per-platform metadata for `cfg` the same way we keep per-platform derivations.

Work with -Z build-std

1

See - https://github.com/rust-lang/wg-cargo-std-aware - https://doc.rust-lang.org/cargo/reference/unstable.html#build-std - https://internals.rust-lang.org/t/dogfooding-z-build-std-in-rustbuild/13775/13 I am very interested using this for nice incremental builds, native and cross, building each crate of the standard library and also rustc...

When cross compiling, one often has a prefixed pkg-config executable that uses a different search path, so host platform and build platform pkg-config files don't get mixed up. (This is...

https://gitlab.haskell.org/ghc/git-haskell-org-hooks there are the linters. It would be nice to have them in the dev shell.

Build misc CI tools for shell

1

This way we can repro more of CI locally. Thanks @jonored for the idea.

Change imports to work with functored AST

19

Unfortunately due to https://gitlab.haskell.org/ghc/ghc/-/issues/19507 this cannot be perfectly seamless