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: avoid allocations in Display and Debug of Multiaddr #106

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

hrxi
Copy link
Contributor

@hrxi hrxi commented Nov 21, 2023

No description provided.

Copy link
Contributor

@thomaseizinger thomaseizinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me, thank you!

Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! Did you stumble upon these in a memory profile?

If you want this as a patch release, mind bumping the version and adding a changelog entry?

@hrxi
Copy link
Contributor Author

hrxi commented Nov 21, 2023

No, just happened to read these implementations by chance, and saw that they allocate. I remembered that we include them in a lot of log messages so I thought it might be worth sending a PR.

Should I also write a changelog entry if I don't need a patch release?

@mxinden
Copy link
Member

mxinden commented Nov 21, 2023

Should I also write a changelog entry if I don't need a patch release?

Fine without. Will be released whenever we cut a new release.

Thank you!

@mxinden mxinden changed the title Avoid allocations in Display and Debug implementations fix: avoid allocations in Display and Debug of Multiaddr Nov 21, 2023
@mxinden mxinden merged commit 38d3a57 into multiformats:master Nov 21, 2023
5 checks passed
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.

None yet

3 participants