Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases. That is why it is better to explicitly return a value. As ...
Answer
#3: Post edited
by
Alexei
·
2021-08-30T16:58:30Z (about 3 years ago)
simplified the answer
Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases and quickly inspecting the function does not make it obvious. That is why **it is better to explicitly return a value**.- As a side note, Languages such as C# and Java prohibit this (compiler error).
- Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases. That is why **it is better to explicitly return a value**.
- As a side note, Languages such as C# and Java prohibit this (compiler error).
#2: Post edited
by
Alexei
·
2021-08-30T16:56:48Z (about 3 years ago)
Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases and quickly inspecting the function does not make it obvious. That is why it is better to explicitly return a value.- As a side note, Languages such as C# and Java prohibit this (compiler error).
- Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases and quickly inspecting the function does not make it obvious. That is why **it is better to explicitly return a value**.
- As a side note, Languages such as C# and Java prohibit this (compiler error).
#1: Initial revision
by
Alexei
·
2021-08-30T16:56:21Z (about 3 years ago)
Not returning a value on all code paths is error-prone because the function might not return the expected value in the non-covered cases and quickly inspecting the function does not make it obvious. That is why it is better to explicitly return a value. As a side note, Languages such as C# and Java prohibit this (compiler error).