Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

chore!: Reorganise compiler in terms of optimisers and transformers #60

Closed

Conversation

joss-aztec
Copy link
Contributor

Related issue(s)

Resolves #59

Description

Summary of changes

Passes that are required for a circuit to be usable--rather than just for improving performance--are now called transformers instead of optimisations.

Transforms:

  • fallback
  • r1cs
  • csat

Optimisations:

  • general
  • more to come

General optimising is now separated into its own pass instead of being executed by r1cs of csat. As a result the r1cs pass current has no work to perform.

Checklist

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt with default settings.
  • I have linked this PR to the issue(s) that it resolves.
  • I have reviewed the changes on GitHub, line by line.
  • I have ensured all changes are covered in the description.

Passes that are required for a circuit to usable, rather than just for improving performance, are now called transformers instead of optimisations.

Transforms:
fallback
r1cs
csat

Optimisations:
general
more to come

General optimising is now separated into its own pass instead of being executed by r1cs of csat. As a result the r1cs pass current has no work to perform.
@kevaundray kevaundray changed the title Reorganise compiler in terms of optimisers and transformers chore: Reorganise compiler in terms of optimisers and transformers Feb 3, 2023
@TomAFrench
Copy link
Member

I really like this reorganisation of the compiler, I'm happy to fix the merge conflicts caused by adding spellcheck. Are there any blockers for this PR after that?

@TomAFrench TomAFrench changed the title chore: Reorganise compiler in terms of optimisers and transformers chore!: Reorganise compiler in terms of optimisers and transformers Feb 10, 2023
@joss-aztec
Copy link
Contributor Author

Are there any blockers for this PR after that?

Not to my knowledge, though I expect this merge will cause conflicts on other branches under review.

@kevaundray
Copy link
Contributor

closing as #88 has been merged

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make organisation of compiler logic clearer
3 participants