You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some functions are allowed to be called with overlapping memory but the documentation does not always specify that. Example: Ed25519::secret_to_public.
The text was updated successfully, but these errors were encountered:
Some functions are allowed to be called with overlapping memory ... Example: Ed25519::secret_to_public.
I just looked at line 25 of the hacl-star source and I think public_key and private_key should not overlap.
Did you mean:
Some functions are not allowed to be called with overlapping memory
Would it also be helpful to slightly improve the documenting comments so the the Params and Returns headings can render when they are converted to docs?
As an example compare the aesthetic look EdDSA against the organized RSAPSS:
Would it also be helpful to slightly improve the documenting comments so the the Params and Returns headings can render when they are converted to docs?
Yeah I agree. The RSA docs are way nicer to read. Organising them would be great.
Again, this needs to be done on the hacl-star side.
Some functions are allowed to be called with overlapping memory but the documentation does not always specify that. Example:
Ed25519::secret_to_public
.The text was updated successfully, but these errors were encountered: