add WIDTH constant to Poseidon2 types for compile-time safety#96
Merged
ch4r10t33r merged 1 commit intoblockblaz:masterfrom Dec 18, 2025
Merged
add WIDTH constant to Poseidon2 types for compile-time safety#96ch4r10t33r merged 1 commit intoblockblaz:masterfrom
ch4r10t33r merged 1 commit intoblockblaz:masterfrom
Conversation
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
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.
Summary
Adds a
WIDTHconstant to Poseidon2 type definitions to enable compile-time width validation.Motivation
Poseidon2 has multiple width variants, but there was no programmatic way to verify which variant a type represents at compile time. This can lead to subtle bugs where code expects one width but receives another.
Benefits