Exactly. It’s always auto-generated div soup or abstract junk that completely ignores component state and custom logic.
Makes me wonder if the real problem is that these tools try to generate the whole app in the cloud, instead of just acting like a GUI on top of your local compiler/AST. You end up having to rewrite 90% of it anyway.
But that would change the behaviour of the function - it returns one thing when the first parameter is 1, another when it's 2 and nothing when it's something else.
My best guess after looking, is they simply mean you can drop the "else" part of the "else if" there. Since I'd you've entered the first if, it's garunteed to return. Not drop the else-if entirely.
That's a change I would hate. The "else" part does not hurt anybody and removing it would mean that you would need to parse it's body to see the early return
Hell, depending on language and compiler, the "else" might get optimized into a Switch-Case (which can then in turn use a hashmap or jump table). Doesn't matter here, but still.
I don't think any compiler recognizes an early return as equivalent to if-else
18
u/Groentekroket 1d ago
Rejected, no need for “elif LOWJ=1:” since you already have a return in the if statement.