You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.
Hi, I've started developing MicroQiskit in Rust which I should finish reasonably soon. I have a question concerning the distribution: most rust libraries are published as crates (like packages in python) on crates.io, making it very easy to add dependencies to a project. Should I implement MicroQiskit as a crate or as just a single file that users can then import? The package route would only generate two additional TOML files.
However, placing it on crates.io means that either I would host a separate GitHub repo with the source, or the owner of this repo would log in to crates.io using GitHub and add the crate as a subdirectory of this repo - ensuring any future changes to the code are reflected on crates.io.
The text was updated successfully, but these errors were encountered:
Hi, I've started developing MicroQiskit in Rust which I should finish reasonably soon. I have a question concerning the distribution: most rust libraries are published as crates (like packages in python) on crates.io, making it very easy to add dependencies to a project. Should I implement MicroQiskit as a crate or as just a single file that users can then import? The package route would only generate two additional TOML files.
However, placing it on crates.io means that either I would host a separate GitHub repo with the source, or the owner of this repo would log in to crates.io using GitHub and add the crate as a subdirectory of this repo - ensuring any future changes to the code are reflected on crates.io.
The text was updated successfully, but these errors were encountered: