Closed TonyValenti closed 5 years ago
Great, I'll check it out and get back to you.
Hi Tony, I've added a few comments for you to comment on but generally looks good.
@andywilsonuk - Thanks Andy. I responded to your items in-line. Do you want me to change them or you? Also, what are your thoughts about the bigger changes I suggested in https://github.com/andywilsonuk/StringTokenFormatter/issues/16 ?
ok, I really like what you've done here around consistency and add more defaults for people to use (like in markers). My only comment is that you've got some inconsistency with parameter names, they should be camelCase but you've got some TitleCase. Considering the size of change I think that's pretty good!
Sounds great! I'll review and get that changed. My preference is for title case. Can I use that or do you have a preference for camel?
Camel is c# standard so let's go with that.
@andywilsonuk I got the changes made! Can you give me permission to merge this in? Also, I've never done a nuget release. Do you want to do that or should I?
Are there any other changes you'd like to see?
Nope I think we are all good. I've added you as contributor now so you should be able to merge the changes. After that I'll create the new nuget package and upload it.
@andywilsonuk - All merged in!
I've created the package and uploaded it to nuget.org, it'll hopefully be available soon.
Well done on a great upgrade!
Hi @andywilsonuk - After doing a bit more profiling, I wasn't able to get the entirity of the performance gains I was hoping for. The compiled value retrieval is much faster than using reflection (and the compilation cost is negligible), however, after further delving I was able to determine that value retrieval was actually not a huge percentage of the operation - string manipulation and looping was.
There are three main changes in this PR:
These enhancements took my tests from taking ~1.9 seconds to run down to about 1.1 seconds.