Add repo for Rust-specific soft fork of Enzyme #1665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently our submodule for Enzyme in
rust-lang/rust
points to an external repository outside of our organization. As we do for LLVM, it would be useful for us to maintain a Rust-specific soft fork of Enzyme withinrust-lang/
. Let's create a repository for this.In particular, this would unblock some work being held up by CI issues on the upstream project, and it'd allow us to make some changes that might better facilitate upstreaming of this work into LLVM.
Probably we should also create a
wg-enzyme
or whatnot team that could maintain this. Alternatively or in addition, we could formalizewg-autodiff
, for which we have a Zulip stream but no entry here. But let's handle that separately. For the moment, we just give access to the normal teams that would be likely to need to touch it, review PRs for it, manage issues on it, etc.CC @oli-obk who seconded the compiler MCP for this work and is overseeing it on that side.
I'm the lang liaison for our approved experiment for this work.
CC @Mark-Simulacrum, @cuviper, @ehuss for thoughts on release and bootstrap and whatnot here.
CC @nikic on the LLVM aspect.
CC @ZuseZ4 who is the owner for this work (and for whom we should find a team at some point).
CC @wsmoses from upstream Enzyme with whom @ZuseZ4 talked this over.