@HiddenLayer555@lemmy.ml to Programmer Humor@lemmy.mlEnglish • 1 day agoWhy make it complicated?lemmy.mlimagemessage-square44fedilinkarrow-up183arrow-down10file-textcross-posted to: programmer_humor@programming.dev
arrow-up183arrow-down1imageWhy make it complicated?lemmy.ml@HiddenLayer555@lemmy.ml to Programmer Humor@lemmy.mlEnglish • 1 day agomessage-square44fedilinkfile-textcross-posted to: programmer_humor@programming.dev
minus-squareCarrotsHaveEarslinkfedilink2•9 hours agoWhat about you declare (then it gets allocated in stack) it and pass it to a different context for assignment?
minus-square@ThirdConsul@lemmy.mllinkfedilink2•edit-26 hours agoWell, I don’t know your use case well enough, but I guess you might have perfect reason for that behavior. One thing that comes to my mind is the old Try in C# bool parsedSuccessfully = int.TryParse("123", out int result); But I guess more popular approach would be to use Error as Values, right? E.g. something like this Outcome<Exception, Int> result = int.TotallyNewParse("123");
What about you declare (then it gets allocated in stack) it and pass it to a different context for assignment?
Well, I don’t know your use case well enough, but I guess you might have perfect reason for that behavior.
One thing that comes to my mind is the old Try in C#
bool parsedSuccessfully = int.TryParse("123", out int result);
But I guess more popular approach would be to use Error as Values, right?
E.g. something like this
Outcome<Exception, Int> result = int.TotallyNewParse("123");