forked from Qiskit/qiskit
-
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.
Add structure for multiple Rust crates (Qiskit#9742)
* Add structure for multiplie Rust extension crates This is a precursor to adding an entirely separate and self-contained crate to handle parsing of OpenQASM 2 (not 3 - this is kind of like a trial run for that). It could conceivably still live within `qiskit._accelerate`, but having separate crates helps us enforce more sane API barriers, and has improvements in the incremental build time when working on only one of the Rust extensions. The intent after this commit is still to have `qiskit._accelerate` as an easy catch-all for accelerators for Python. Developers should not need to be concerned with defining a new crate for every new feature, and for the most part `_accelerate` is still logically interoperative within itself (for example, `NLayout` is used all over). This is just laying out the groundwork so more complex crate additions _can_ also be made. Some of the niceties to do with Cargo workspaces only became stabilised in Rust 1.64. In particular, inheritance from the workspace root for things like the package version, Rust version, and dependencies only came in then. For now, the `workspace.packages` key in the root `Cargo.toml` is ignored with a small warning during the build, but I've put it in place mostly to keep track of what we can change once the MSRV becomes 1.64 or greater (likely not til at least Terra 0.26). * Add README.md to crates/accelerate * Correct licence metadata
- Loading branch information
1 parent
2553376
commit c6cd0d5
Showing
28 changed files
with
119 additions
and
83 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
[package] | ||
name = "qiskit_accelerate" | ||
# The following options can be inherited with (e.g.) `version.workspace = true` once we hit Rust | ||
# 1.64. Until then, keep in sync with the root `Cargo.toml`. | ||
version = "0.24.0" | ||
edition = "2021" | ||
rust-version = "1.61" | ||
license = "Apache-2.0" | ||
|
||
[lib] | ||
name = "qiskit_accelerate" | ||
crate-type = ["cdylib"] | ||
|
||
[dependencies] | ||
rayon = "1.7" | ||
numpy = "0.18.0" | ||
rand = "0.8" | ||
rand_pcg = "0.3" | ||
rand_distr = "0.4.3" | ||
ahash = "0.8.3" | ||
num-complex = "0.4" | ||
num-bigint = "0.4" | ||
rustworkx-core = "0.12" | ||
|
||
# The base version of PyO3 and setting a minimum feature set (e.g. probably just 'extension-module') | ||
# can be done in the workspace and inherited once we hit Rust 1.64. | ||
[dependencies.pyo3] | ||
version = "0.18.1" | ||
features = ["extension-module", "hashbrown", "indexmap", "num-complex", "num-bigint"] | ||
|
||
[dependencies.ndarray] | ||
version = "^0.15.6" | ||
features = ["rayon"] | ||
|
||
[dependencies.hashbrown] | ||
version = "0.13.2" | ||
features = ["rayon"] | ||
|
||
[dependencies.indexmap] | ||
version = "1.9" | ||
features = ["rayon"] |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# `qiskit._accelerate` | ||
|
||
This crate provides a bits-and-pieces Python extension module for small, self-contained functions | ||
that are used by the main Python-space components to accelerate certain tasks. If you're trying to | ||
speed up one particular Python function by replacing its innards with a Rust one, this is the best | ||
place to put the code. This is _usually_ the right place to put Rust/Python interfacing code. | ||
|
||
The crate is made accessible as a private submodule, `qiskit._accelerate`. There are submodules | ||
within that (largely matching the structure of the Rust code) mostly for grouping similar functions. | ||
|
||
Some examples of when it might be more appropriate to start a new crate instead of using the | ||
ready-made solution of `qiskit._accelerate`: | ||
|
||
* The feature you are developing will have a large amount of domain-specific Rust code and is a | ||
large self-contained module. If it reasonably works in a single Rust file, you probably just want | ||
to put it here. | ||
|
||
* The Rust code is for re-use within other Qiskit crates and maintainability of the code will be | ||
helped by using the crate system to provide API boundaries between the different sections. | ||
|
||
* You want to start writing your own procedural macros. |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
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