Releases: linkdotnet/StringBuilder
Releases Β· linkdotnet/StringBuilder
v1.6.0
Addeed
- Added overload which allows an initial string for the ValueStringBuilder
- Meziantou.Analyzer as developer dependency to spot issues early on
readonlyhint's on readonly methods
Changed
- Added
StructLayout(LayoutKind.Auto), which makes the ValueStringBuilder not usable for unmanaged code
v1.5.1
Added
- Hot path optimization for strings
v1.5.0
Added
- New easy API for concatenating smaller strings or objects via
ValueStringBuilder.Concat("Hello", " ", "World"); - Smaller performance improvements in internal API's
v1.4.1
Added
- Smaller internal API improvements
- Smaller performance improvements
v1.4.0
Added
- Added the
scopedkeyword to simplify code and allow more scenarios for the user
Fixed
Growallowed values, which would truncate the internally represented string
v1.3.0
Fixed
- Fixed an issue where memory is not returned to the ArrayPool
- Fixed an issue where memory could be overwritten, giving the chance to tamper with the internal array
v1.2.0
Added
ValueStringBuilderconstructor can take initial buffer instead of creating it itself.- More compiler hints for inlining.
v1.1.0
Added
Containsmethod.
Fixed
- Smaller tweaks in CI/CD
IndexOfandLastIndexOfdid not return 0 when passing an empty string. Now it is aligned tostring.IndexOf.
Removed
- Debug symbol package (snupkg) due to the many constraints of NuGet.org
v1.0.1
Added
- Enabled some optimization hints for the compiler.
- Include debug symbols when publishing to NuGet for easier debugging experience
v1.0.0
Added
LastIndexOfto find the last occurence in the represented string.ReplaceGeneric<T>added for generic replacement in the string builder. Can have performance / allocation penalties in comparison to the non-generic version.