Removes allocation when using IntPtr and Nullable<T>. #24
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.
IntPtr
IntPtr does not support formatting, but it is the "basic" numeric type of the system.
However, when used with ZString, it causes a heap allocation.
I believe there needs to be built-in support for it.
The specification of IntPtr.ToString() is quoted below.
Before
After
The benchmark code is as below.
Nullable<T>
String.Format supports formatting for Nullable types.
In ZString Ver2.1.3, heap allocation occurs.
Before
After
The benchmark code is as below.
IFormattable
For convenience, If you implement IFormattable, call
ToString(string format, IFormatProvider formatProvider)
.However, allocation will occur.