One thing I don't understand is why you used StringBuilder in ParseSectionAs* in the first place.
Wasn't it be easier and more efficient just call a Substring?
- Performance & optimisation is my wheelhouse
- Passionate about technical excellence
- Extreme programming & lean software development
- Trust in the scientific method
I suspect although have not confirmed that using string.Substring instead of StringBuilder would have worst characteristics. Hopefully I will get time to write a follow up article with everyone's ideas and suggestion.
In the mean time feel free to have a go yourself. A couple of people have already started sent a pull requests.
Regards,
Indy
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for posting!
Very interesting.
One thing I don't understand is why you used StringBuilder in ParseSectionAs* in the first place.
Wasn't it be easier and more efficient just call a Substring?
Hi Vadim,
I suspect although have not confirmed that using
string.Substringinstead ofStringBuilderwould have worst characteristics. Hopefully I will get time to write a follow up article with everyone's ideas and suggestion.In the mean time feel free to have a go yourself. A couple of people have already started sent a pull requests.
Regards,
Indy