[OT] Keeping algorithm and optimisations separated

[renoX]

Hello,

one common issue when you optimize code is that the code becomes 
difficult to read/maintain, but if you're trying to process 
images there may be hope: Halide is a DSL (currently embedded in 
C++) which keep the algorithm and the "optimization 
recipe"(schedule) separated AND the performance can be similar to 
hand-optimized C++ code.

You can read more about Halide here: http://halide-lang.org/

Regards,
renoX

PS: I'm not related at all with the Halide's developers but I 
thought this is an interesting topic.