Explore >> Select a destination
|
You are here 
|
www.cplusplus.com | ||
| | | | |
fzakaria.com
|
|
| | | | | Bazel is a pretty amazing tool but it's definitely full of it's warts, sharp edges and arcane knowledge. The appeal to most who adopt Bazel is the ability to memoize much of the build graph if nothing has changed. Furthermore, while leveraging remote caches, build results can be shared across machines making memoization even more effective. This was a pretty compelling reason to adopt Bazel but pretty soon many noticed, especially on their CI systems, lots of unecessary data transfers for larger codebases. ?? If the network is poor, the benefits of remote caching (memoization) can be outweighed by the cost to download the artifacts. | |
| | | | |
outflux.net
|
|
| | | | | ||
| | | | |
blog.oddbit.com
|
|
| | | | | Overview I was recently working with someone else's C source and I wanted to add some basic error checking without mucking up the code with a bunch of if statements and calls to perror. I ended up implementing a simple must function that checks the return value of an expression, and exits with an error if the return value is less than 0. You use it like this: must(fd = open("textfile.txt", O_RDONLY)); Or: | |
| | | | |
www.windytan.com
|
|
| | | A blog about signals, programming, music, and other stuff. | ||
