Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix warnings related to dangling comments and lossy conversions #268

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jasonkatonica
Copy link
Member

Recently numerous warnings have displayed related to lossy conversions and dangling javadoc comments.

This update ensures that there are no dangling javadoc comments these changes fall into various categories such as unused code that has javadoc comments embedded, empty javadoc comments, duplicate javadoc comments, or javadoc comments that are not located above a declaration.

Updates were also made to XDHPublicKeyImpl, BaseTestChaCha20KAT, and BaseTestChaCha20NoReuse to explicitly cast an int to a byte OR make use of a common utility function BaseUtils.hexStringToByteArray that does not have such a lossy conversion present.

While fixing dangling comments one test testRSASignatureSHA512_256 was found to be commented out. It appears to execute correctly and does seem like a valid test so this test was uncommented.

Two spaces found in the pom.xml were removed for consistency.

Signed-off-by: Jason Katonica [email protected]

Recently numerous warnings have displayed related to lossy conversions
and dangling `javadoc` comments.

This update ensures that there are no dangling `javadoc` comments these
changes fall into various categories such as unused code that has
`javadoc` comments embedded, empty `javadoc` comments, duplicate
`javadoc` comments, or javadoc comments that are not located above a
declaration.

Updates were also made to `XDHPublicKeyImpl`, `BaseTestChaCha20KAT`,
and `BaseTestChaCha20NoReuse` to explicitly cast an int to a byte OR
make use of a common utility function `BaseUtils.hexStringToByteArray`
that does not have such a lossy conversion present.

While fixing dangling comments one test `testRSASignatureSHA512_256` was
found to be commented out. It appears to execute correctly and does seem
like a valid test so this test was uncommented.

Two spaces found in the pom.xml were removed for consistency.

Signed-off-by: Jason Katonica <[email protected]>
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.

1 participant