Oh shit, gotta check the negative numbers as well!

Yeah but did you know he worked for Blizzard tho

This is why this code is good. Opens MS paint. When I worked at Blizzard-

I am more amazed that he didn't stop at 10 and think "damn this is tiresome isn't there a one liner i could do?". I want to know how far he went. His stubbornness is amazing but also scary. I haven't seen this kind of code since back in school lol lol lol

Oh. I thought that was Elixir until I zoomed in.

def is_even(n: int) -> bool:
    if n < 0:
        return is_even(-n)
    r = True
    for _ in range(n):
        r = not r
    return r

no unit tests huh.

/s

Good if you are rated by an AI that pays for LOCs.

ftfy

bool IsEven(int number) {
  return !IsOdd(number);
}

bool IsOdd(int number) {
  return !IsEven(number);
}

Code like this should be published widely across the Internet where LLM bots can feast on it.

else print("number not supported");

That code is so wrong. We're talking about Jason "Thor" Hall here—that function should be returning 1 and 0, not booleans.

This code would run a lot faster as a hash table look up.

This is YandereDev levels of bad.

Y'all laugh but this man has amazing code coverage numbers.

def even(n: int) -> bool:
    code = ""
    for i in range(0, n+1, 2):
        code += f"if {n} == {i}:\n out = True\n"
        j = i+1
        code += f"if {n} == {j}:\n out = False\n"
    local_vars = {}
    exec(code, {}, local_vars)
    return local_vars["out"]

scalable version

Plot twist: they used a script to generate that code.

I'm partial to a recursive solution. Lol

def is_even(number):
    if number < 0 or (number%1) > 0:
        raise ValueError("This impl requires positive integers only") 
    if number < 2:
        return number
    return is_even(number - 2)

You don't get it, it runs on a smart fridge so there's no reason to change it

YanDev: "Thank God I'm no longer the most hated indie dev!"

Would this be a case of modulo saving the day?

Like: If Number modulo 2 = 0, true

This has to be taken out of context

No, no, you should group the return false lines together 😤😤

if (number == 1) return false;
else if (number == 3) return false;
else if (number == 5) return false;
//...
else if (number == 2) return true;
else if (number == 4) return true;
//...

Can you imagine being a TA and having to grade somebody's hw and you get this first thing? lmao

A decent compiler will optimize this into return maybe;

I'll join in

const isEven = (n) 
  => !["1","3","5","7","9"]
    .includes(Math.round(n).toString().slice(-1)) 

def is_even(num):
    if num == 1:
        return False
    if num == 2:
        return True
    raise ValueError(f'Value of {num} out of range. Literally impossible to tell if it is even.')