release: publish to crates.io?

[Autoparallel]

It seems like it wouldn't take too much work to publish most of these crates to crates.io.

There's some odd exceptions for certain github based dependencies:

• noname
• ark-circom
  Are the main ones I'd worry about. I believe acvm could be taken from crates.io as well (though it would be worth communicating with Noirlang team.

Easiest move forward would be to feature gate: noname and circom

Then could publish without those features and add in later as needed and update default-features too.

Thoughts?

[arnaucube]

Yes ^^ Thanks for proposing this!
Currently we're doing an iteration trying to polish a bit the interfaces (till now interfaces have been unstable and changing often) and optimizing a bit to reduce proving times, with the aim of publishing a first initial release (in github) of the library by the end of January / beginning of February. Maybe once we have this first release we can publish it to crates.

Regarding noname & circom (and noir too), those are under the 'experimental-frontends' directory, so we can probably keep them out from crates for the time being.

[Autoparallel]

I personally don't see harm in releasing a sonobe-frontends crate v0.1.0 to crates.io so long as there's clear guidance that these are experimental. But, that's just my two cents.

As for releasing in general, release-plz is super nice when combined with cargo-semver and even if you all decide to keep manipulating the APIs, a new version release being automated isn't bad!

Let me know if you want help on this and I can get started on it! Otherwise, I'll eagerly wait Jan/Feb to roll around :)