-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This is an in-progress transplant of guppy from using an ad-hoc `Hugr` definition into the builder from the `hugr` library. The main mismatch between the old and new builders is that guppy used to lazily add typed ports to the graph nodes as it needed. Since the new builder requires operations to define their signature, we end up having to edit the code everywhere from `guppylang.compiler` to the `guppylang.prelude` definitions. My first goal is to get this working, and then I will try and split some changes from this PR (although most of it will have to be merged monolithically). Current test status: - 390 $\color{green}\text{passed}$ - 14 $\color{yellow}\text{skipped}$ - 0 $\color{red}\text{failed}$ These issues currently breake some tests. I'll fix them before merging the PR - CQCL/hugr#1319 ~~Required to store the module names in the hugr metadata~~ - CQCL/hugr#1424 ~~Required for pytket and llvm integration~~ - ~~Release hugr and tket2 with the latest changes~~ Closes #257. Closes #85 BREAKING CHANGE: Removed `guppylang.hugr_builder.hugr.Hugr`, compiling a module returns a `hugr.Hugr` instead. --------- Co-authored-by: Mark Koch <[email protected]>
- Loading branch information
Showing
42 changed files
with
1,501 additions
and
2,152 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.