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

ftfy

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

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

else print("number not supported");

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

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;
//...

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

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

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

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)

A decent compiler will optimize this into return maybe;

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

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.')

pro hacker tip: you can optimize this by using "num" for the variable name instead of "number"

This is YandereDev levels of bad.

pff, i aint reading all that, lemme optimize it:

private bool isEven(int number) {
    return rand() < 0.5;
}

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

Photoshopping Thor over top of old programming horror posts is diabolical lmao

This is what Test Driven Development looks like

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

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

Ffs just use a switch. It's much faster!

I'll join in

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

assert IsEven(-2);

No need to reinvent the wheel. Use the isEven API!

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

You could use a loop to subtract 2 from the number until it equals one or zero

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

What you do is use a for loop to generate a million lines for you, then paste it in. Writing it manually is moronic. You can easily make it support numbers above 1,000,000 too this way, talking about scalable

IMO he's ragebaiting

no unit tests huh.

/s