Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Don't use viper.Get* in tight loops #2495
Profiling indicate that using
Just removing one viper.Get temporary from
referenced this issue
Sep 26, 2016
I have "suggested" this for the 0.17 release -- but it is probably a more natural fit for the next ... My PR isn't entirely finished, but I will wrap it up during the day.
I'm not sure why Viper allocates memory on a simple
With the fix in
This is the delta after the latest Viper update:
Still worth doing, but not super-important anymore.