Not all code paths return a value

Arcade Help
1

image
image966Ă—181 22.4 KB

What is the error?

2

Say we pass in w to WhatToGet.

Then it won’t execute return*.

That’s a problem.

*Well technically it will automatically return something but IDK what it is in TypeScript. In Python, that would be None which is TypeScript’s null.

3

So if I put an else, it will work?

4

You need to always return something no matter what happens in the function. And they have to be the same type.

So something like this:

function foo(x: number): boolean {
    if (x== 0) {
        return true
    }
}

Will give an error, because x can be 1, so it won’t execute return true.

Something like this:

function foo(x: number): boolean {
    if (x== 0) {
        return true
    } else {
        return false
    }
}

Will be syntactically correct. But notice how true and false are both booleans. You couldn’t do this:

function foo(x: number): boolean {
    if (x== 0) {
        return true
    } else {
        return "bad value"
    }
}
5

But you could do

if (ReturedValue == 0) {
        splash ("Bad Vaue")
   
    }

Right?

6

Are you in a function? You will still need to return a value.

7

No, separate.

8

Yes, but you still have the problem with your original function.

9

Yes If your function sometimes returns a value then It will get confused, If you use (if returned value == 0 then “bad value…”) that will be fine.

10

But you always have to return or not return.

11

Oh, I fixed that with the else statment.

1 Like
12

At all times, you have to put return blocks at the end of a function if you have another return block at the end