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

[CodeHealht][wallet] Avoid NoDestructor in eth_data_builder.cc #26683

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

cdesouza-chromium
Copy link
Collaborator

The use of NoDestructor for a map of strings in ChainIdToVersion is wasteful of resources, when the actual data can be seen at compile time.

This PR converts this static std::map into a fixed flat map. This required changing the type of the elements to string_view, so this PR goes a bit the extra mile to modernise some of the functions around to use string_view.

Resolve brave/brave-browser#42432

Resolves

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally:
    • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
    • npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

The use of `NoDestructor` for a map of strings in `ChainIdToVersion` is
wasteful of resources, when the actual data can be seen at compile time.

This PR converts this static `std::map` into a fixed flat map. This
required changing the type of the elements to `string_view`, so this PR
goes a bit the extra mile to modernise some of the functions around to
use `string_view`.

Resolve brave/brave-browser#42432
Copy link
Member

@SergeyZhukovsky SergeyZhukovsky left a comment

Choose a reason for hiding this comment

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

++

@cdesouza-chromium
Copy link
Collaborator Author

cdesouza-chromium commented Nov 21, 2024

++

Thanks mate.. you are always ready in reviewing things.

@cdesouza-chromium cdesouza-chromium merged commit a70a0b2 into master Nov 21, 2024
18 checks passed
@cdesouza-chromium cdesouza-chromium deleted the avoid-unnecessary-nodestructor-pt1 branch November 21, 2024 23:28
@github-actions github-actions bot added this to the 1.75.x - Nightly milestone Nov 21, 2024
@brave-builds
Copy link
Collaborator

Released in v1.75.43

cdesouza-chromium added a commit that referenced this pull request Nov 22, 2024
This function has been returning a vector of strings, to be used by
`GetMany`, and therefore a `NoDestructor` instance is needed. However,
the only reason why this has to be a vector of strings is because in the
end `EncodeStringArray` requires a vector of strings.

This PR changes `EncodeStringArray` to take spans of strings and of
string views. This will allows to convert the keys into a `constexpr`
value, and avoid the use of `NoDestructor`.

In a follow up PR, additional callsites of `EncodeStringArray` may be
migrated to the `string_view` variant.

This is a follow up of these PRs:
#26683
#26688

Resolves brave/brave-browser#42453
cdesouza-chromium added a commit that referenced this pull request Nov 22, 2024
This function has been returning a vector of strings, to be used by
`GetMany`, and therefore a `NoDestructor` instance is needed. However,
the only reason why this has to be a vector of strings is because in the
end `EncodeStringArray` requires a vector of strings.

This PR changes `EncodeStringArray` to take spans of strings and of
string views. This will allows to convert the keys into a `constexpr`
value, and avoid the use of `NoDestructor`.

In a follow up PR, additional callsites of `EncodeStringArray` may be
migrated to the `string_view` variant.

This is a follow up of these PRs:
#26683
#26688

Resolves brave/brave-browser#42453
cdesouza-chromium added a commit that referenced this pull request Nov 23, 2024
This function has been returning a vector of strings, to be used by
`GetMany`, and therefore a `NoDestructor` instance is needed. However,
the only reason why this has to be a vector of strings is because in the
end `EncodeStringArray` requires a vector of strings.

This PR changes `EncodeStringArray` to take spans of strings and of
string views. This will allows to convert the keys into a `constexpr`
value, and avoid the use of `NoDestructor`.

In a follow up PR, additional callsites of `EncodeStringArray` may be
migrated to the `string_view` variant.

This is a follow up of these PRs:
#26683
#26688

Resolves brave/brave-browser#42453
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove unnecessary NoDestructor static in eth_data_builder.cc
3 participants