feat(eventsub): use custom String type
#5968
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements the type I sketched in #5921. It's either a
QString, an allocatedchar[], or an in-placechar[]. I documented the class a bit to explain how it works. The benchmark runs equally fast.For Windows debuggers, there's also a natvis visualizer. I don't know how GDB ones work, but that might be doable as well (i.e. putting them in the debug info/a special section).
I previously added ASAN to the Windows CI. We could do that in a followup PR.
This might be the first change that will require Qt 6, because it uses
QAnyStringView.Closes #5921.