And would add that for me, making a function that returns void is a way of declaring that that particular function is impure and will most likely be made to do side effects stuff.... cause we need to do them sometimes:)
that particular function (...) will most likely be made to do side effects stuff
I thought that this can be solved by changing the signature?
Example:
template<typenameT>voidprocessThenOutputConcatenatedInputVariables(Tvar1,Tvar2){process(var1,var2);// side effect covered by the signaturestd::cout<<var1<<var2;}
Unfortunately the signature wont make this function pure.
What you would need in this case is composition which would allow you to compose 2 functions. I will at one point cover composition, in the mean time, you can read that great article by Eric Elliott --> medium.com/javascript-scene/master...
Hey! I'm YCMJason, a Software Engineer in London 👨💻. Love diving into tech puzzles and sharing them! 🧩
All views expressed here are my own opinions, so please take them with a pinch of salt! 🧂
Yes I would say that Luka is right.
And would add that for me, making a function that returns void is a way of declaring that that particular function is impure and will most likely be made to do side effects stuff.... cause we need to do them sometimes:)
I thought that this can be solved by changing the signature?
Example:
Unfortunately the signature wont make this function pure.
What you would need in this case is
compositionwhich would allow you to compose 2 functions. I will at one point cover composition, in the mean time, you can read that great article by Eric Elliott --> medium.com/javascript-scene/master...Why not?
@tuxOr
There is nothing to do with the signature of a function.
A function is pure if and only if
So in your example, assuming
process(var1, var2)will make some side effect somewhere else in the program, it is not a pure function.However, if
processdo not make any changes, then it will still be a pure function.I think I understood now, thank you!