|
You are here |
www.cppstories.com | ||
| | | | |
www.bfilipek.com
|
|
| | | | | Thank you for all the comments about the string_view performance! Last week I got a lot of feedback on how to improve the initial string split code. Have a look at how can we update the code and get some better performance. Intro Last week I showed a few examples of string_view. | |
| | | | |
solarianprogrammer.com
|
|
| | | | | How to compile from sources GCC 10 on macOS Catalina | |
| | | | |
disq.us
|
|
| | | | | In this text we'll have a look at a few examples that compare std::string_view against std::string. How much is std::string_view faster than standard std::string operations? Intro I was looking for some examples of string_view, and after a while, I got curious about the performance gain we might get. string_view is conceptually only a view of the string: usually implemented as[ptr, length]. | |
| | | | |
www.adamalbrecht.com
|
|
| | | As my work has transitioned from traditional web apps to thick-client Javascript apps (primarily using Angular), Grunt has become essential in my workflow. Grunt is a nice tool and it gets the job done. But there was always something I didn't like about it that I couldn't quite articulate until I discovered Gulp.js. Whereas in Grunt, you create a json configuration file, Gulp is just a script. It's code. And it really fits my programmer brain better. In this post, I'll convert a basic Gruntfile that compiles and minifies Coffeescript into Gulp. | ||