refactor: cargo workspace organisation

[lonerapier]

Is your feature request related to a problem? Please describe.

Ronkathon, now contains, many different flavors of cryptography, i.e. algebra, primitives (polynomial, curves, tree) encryption standards, hash functions, signatures, pcs, etc.

Creating minimal workspace based abstraction will allow us to orgranise changes easily

Describe the solution you'd like

Should create workspaces for different sections of the code. Possibly:

• primitive
  • field
  • polynomial
  • trees
• standards
  • encryption
  • signature
  • hashes
  • mac
• codes
• pcs
• examples
• benches

Open to any other alternative solution. Let's discuss!!

[Autoparallel]

Yeah, it's worth doing something like this and we can take the following model that many other ecosystems do. For example, we have a few clear crate options:

• ronkathon-primitives
• ronkathon-standards

Then since we have ronkathon, we can just re-export those crates through ronkathon so that working with this is easier.

We should discuss a proper breakdown here. My thoughts are:

• ronkathon-primitives:
  • Algebra (field, rings, group, etc.)
  • Polynomials
  • Vectors/Matrices/Tensors
• ronkathon-standards:
  • encryption
  • signatures
  • hashes
  • codes
  • commitments
• ronkathon-bin
  • benches
  • examples
  • interactive usecases (e.g., let people encrypt and sign data locally!)

What do you think?

[mahmudsudo]

Is anyone taking on this at the moment ?

[Autoparallel]

No, this is still in discussion at the moment. Let's settle on an organization style first then we can do it.

Happy to assign you at that point @mahmudsudo .

Do you have any feedback on these? curious how you'd go about it now that you're quite familiar with the codebase.