Re:Relive: 50 years of C, the good, the bad and the ugly
by menaerus on Friday December 30, 2022 @01:49PM
(#34188423)
Of course, you can do it that way as well. However the problem with promise approach is that it is introducing extra dynamic memory allocations beneath and these cannot be optimized out or elided. At least, not to my knowledge. With expression templates and operator overloading you're basically avoiding exactly that as much as possible.
Re:Relive: 50 years of C, the good, the bad and the ugly
by Someone on Friday December 30, 2022 @03:15PM
(#34189503)
Where do you see dynamic memory allocations being needed in that example? I only see locals that a good compiler can fairly easily optimize away.
Also, there’s a simple bijection between expressions with operators and two-argument function calls:
a + b * c
+(a, *(b,c))
plus(a, times(b,c))
Because of that, I don’t understand why operator overloading should give better optimization opportunities than function calls.
I don’t understand that. You can have functions that return promises that then can get passed to other functions returning promises, and leave it either to the compiler or to an expression evaluator you write (that ideally runs at compilation time as much as possible) to optimize away anything not needed. For example (pseudo-code)
in the end, could do the equivalent of I think you could make a modern C++ compiler do that for this simple example.