You’re writing extremely bad code if that’s the case and you need to refactor. The point of a function is to return a value. Anything else is just there to waste cycles and make the code less readable. You should also never use else statements for arithmetic due to their massive relative overhead. Your processor can do multiple arithmetic operations in the time it takes to process one if statement, and don’t get me started on people who demand you use nested if even though switch statements are way faster and leagues more readable.
Those who are the most wrong have the strongest conviction
EDIT: I make a lot of edits because unlike you, I care about the quality and accuracy of what I write. You’re going to spend like an extra 10 minutes tops writing for something that will be read by thousands for years to come. It’s basic courtesy.
god forbid anyone do multiple non-nested if blocks one after another in the same function as the function does multiple different things or (horror of horrors) put an if-else inside a loop
also unless your compiler is completely and utterly brain dead (as is the case with Python, Java, C#, and most other languages that only pretend to be compiled compile to bytecode) a switch and a series of elif statements will compile to the exact same sequence of machine instructions. you can check on godbolt.org if you don’t believe me.
modern compilers are insanely smart. as an example, this loop counts the number of 1’s in the binary representation of a number:
while (n)
{
n = n & (n - 1); // clear the least significant bit set
count++;
}
LLVM will recognize that this is what you are trying to do and emit a single POPCNT instruction on x86, eliminating the loop entirely.
also how would you even use if statements for arithmetic at all? you aren’t thinking of that one joke isEven() function, are you?
Screw else statements, people who use if-return have 180% more readable code.
Because everyone knows a function stops at the if-else. Nothing ever happens afterward.
You’re writing extremely bad code if that’s the case and you need to refactor. The point of a function is to return a value. Anything else is just there to waste cycles and make the code less readable. You should also never use else statements for arithmetic due to their massive relative overhead. Your processor can do multiple arithmetic operations in the time it takes to process one if statement, and don’t get me started on people who demand you use nested if even though switch statements are way faster and leagues more readable.
I disagree but you do you.
Edit: dammit you edit your comment a lot for someone who claims to know how to write code properly.
Those who are the most wrong have the strongest conviction
EDIT: I make a lot of edits because unlike you, I care about the quality and accuracy of what I write. You’re going to spend like an extra 10 minutes tops writing for something that will be read by thousands for years to come. It’s basic courtesy.
…and the self-awareness finally hits
Yeah i’m starting to remember why I quit. In any other industry toxic shit like this goes sinks to the bottom, not the top.
Like seriously, what were you hoping to accomplish with this one? The thread ended yesterday. That’s reddit tier douchery.
god forbid anyone do multiple non-nested if blocks one after another in the same function as the function does multiple different things or (horror of horrors) put an if-else inside a loop
also unless your compiler is completely and utterly brain dead (as is the case with Python, Java, C#, and most other languages that
only pretend to be compiledcompile to bytecode) a switch and a series of elif statements will compile to the exact same sequence of machine instructions. you can check on godbolt.org if you don’t believe me.modern compilers are insanely smart. as an example, this loop counts the number of 1’s in the binary representation of a number:
while (n) { n = n & (n - 1); // clear the least significant bit set count++; }LLVM will recognize that this is what you are trying to do and emit a single
POPCNTinstruction on x86, eliminating the loop entirely.also how would you even use if statements for arithmetic at all? you aren’t thinking of that one joke isEven() function, are you?
It’s much more readable when you use else depending on the checks. You can still use return in an else block.
def Allowed()print(Allowed())`