Hi, I'm not sure if more platforms are interesting to you, but I've made a slightly more complete implementation of padding a struct to the cache line size here:

https://github.com/tinco/cache_line_size

I got the information on the cache line sizes from the Go compiler repository, so I'm pretty sure these are correct for all platforms Go runs on, which is a whole bunch.

Gamma correction is among the things most often done wrong by graphics programming novices. It's almost as bad as missing scene-related color transforms and linear volume sliders in the average video game. The code example in the readme should definitely mention to adjust.Gamma(img, 1/2.2) before doing any color mixing and adjust.Gamma(img, 2.2) before saving back to file (for as long as _bild

I've noticed that www.threadingbuildingblocks.org effectively disappeared as it is redirected to this GitHub repo. Many StackOverflow answers (like 1 2 3 and their comments below like here) suffer now having

It would be useful to see how riko compares to other stream processors. Possible metrics to track are open sockets, bandwith, CPU, and memory usage.

Try to add anchor links to table rows in documentation (specifically for performance counters, to allow linking to specific counters).

Just opening this as a reminder for myself. Someone knowledgable in sphinx and restructuredtext can feel free to do it as well.

It would be nice if someone can extend the readme file with proper conversion.

Crash java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Unable to load script from assets 'threads/pre-load-data-worker.thread.bundle'. Make sure your bundle is packaged correctly or you're running a packager server.

![screen shot 2018-07-28 at 11 29 18](https://user-images.githubusercontent.com/3612098/43357535-8379af28-9259-11e8-9c5a-96

Spotted in the gitter channel

The big thing for me was that it wasn't clear that the cache could be reused. It talks about the state monad and the cache being immutable which caused me to make some bad assumptions, even after diving into the code.

This should be more explicit and clear to not confuse people.

Maybe something that searches for all *.jpeg in a directory, starts a thread pool, and in each thread, converts them to .png

When num_tiles > range.size(), tile_evenly() should first clamp(num_tiles, range.size()).

Otherwise, we may end up with a tiling that isn't a tiling, or somehow doesn't make sense otherwise.

Plasma currently allows _ for function parameter names, but this makes less sense with Plasma than something with clauses such as ML or Prolog. We should probably remove it simplifying the language. This will (for now) not provide a way for programmers to avoid unused argument warnings, but we can add other ways to suppress these.