docs(gr1cs): correct InternedField representation; remove misleading 64-bit bit layout#418
Open
Forostovec wants to merge 1 commit into
Conversation
…64-bit bit layout
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docstring above InternedField incorrectly described a 64-bit bit-packed layout with tag bits, inline small constants (two’s complement), and a “coefficient pool index.” In reality, InternedField is a u32 opaque handle with special cases: 0 => F::ONE, 1 => -F::ONE, and >=2 indexing into FieldInterner::vec. No bit tagging or inline-constant encoding is implemented anywhere in the codebase. Updated the documentation to reflect the actual design to prevent developer confusion.