Skip to content

Conversation

@Rumata888
Copy link
Contributor

Description

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.

Checklist:

  • I have reviewed my diff in github, line by line.
  • Every change is related to the PR description.
  • The branch has been merged with/rebased against the head of its merge target.
  • There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
  • There are no circuit changes, OR a cryptographer has been assigned for review.
  • New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
  • If existing code has been modified, such documentation has been added or updated.
  • No superfluous include directives have been added.
  • I have linked to any issue(s) it resolves.
  • I'm happy for the PR to be merged at the reviewer's next convenience.

@Rumata888 Rumata888 force-pushed the is/optimizing_pcs_build branch from 62ff20f to 99aed8b Compare June 22, 2023 18:17
@kevaundray kevaundray changed the title refactor: Optimizing pcs build refactor: Optimizing build times for polynomial commitment scheme module Jun 26, 2023
@kevaundray
Copy link
Contributor

kevaundray commented Jun 26, 2023

Changed the title to avoid usage of the acronym (pcs) and to be a bit more readable since its going in the changelog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants