-
Notifications
You must be signed in to change notification settings - Fork 381
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
Deprecate merkle packages #2715
Conversation
3cac284
to
9c4b768
Compare
Hmm, I wonder how to silence the self-warnings about deprecated packages using themselves. |
There must be some "silencing" annotations for golangci linter. |
c3a042c
to
dbd34c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does merkle/compact/nodes.go also need to be annotated?
@jiggoha It's ok to annotate only one file per package, because the package comments are "global" within package. So, a single comment in one file deprecates the entire package. |
Trillian is using https://github.com/transparency-dev/merkle. The
merkle
packagesin Trillian will be removed in next releases.
Part of #2338.
Checklist