D'oh. Absolutely right. that's why I should have used something like this: public static string Concat(int x, double y) => $"{x},{y}"; Func concat = Maths.Concat;
I didn't name them, but I think actions might be a better name. Procedures implies state change (at least to me) whereas "Action" seems more generic (it could be for logging, etc.).
This was excellent. Thank you.
Glad you enjoyed it!
Thank you for such a good explanation.
You are welcome!
Thought last param is out in func
D'oh. Absolutely right. that's why I should have used something like this:
public static string Concat(int x, double y) => $"{x},{y}";
Func concat = Maths.Concat;
Excellent tutorial!!
Glad you liked it!
Good job.
Many many thanks
Perfect as usual.
Wow, thank you!
Nice, thanks!
No problem!
hmm... btw, why do they call them Actions? why not Procedures, which was initially used for ones with no return type? :)
I didn't name them, but I think actions might be a better name. Procedures implies state change (at least to me) whereas "Action" seems more generic (it could be for logging, etc.).
@@swildermuth yep, i see your point. makes sense.
promo code doesn't seem to work
DAYOFASPIRE should work for 20% off.