Hello to you all,

In checkpoint 4 I managed to solve the solution after much thinking, looking for missing pieces of information in past lectures and even googling (in other languages). I came up with a solution that seems too verbose especially after seeing the solution from Paul Hudson.

Code:

import Cocoa

enum squareError: Error {
    case outOfBounds, noRoot
}
func squareRoot(firstNum: Int) throws -> Int {
    var result = 0

    for i in 1...10_000 {
        let powerOfTwoResult = i * i
        if firstNum < 1 || firstNum > 10_000 {
            throw squareError.outOfBounds

        } else if powerOfTwoResult != i * i {
            throw squareError.noRoot

        } else if powerOfTwoResult == firstNum {
            result = i
            print("The square root of \(firstNum) is \(result)")

        }
    }
    return result
}

do {
    try squareRoot(firstNum: 25)
} catch squareError.outOfBounds {
    print("Out of bounds.")
} catch squareError.noRoot {
    print("Could not find square root.")
}

Something in my brain tells me this is just a bad solution, too much clutter. I used else ifs but paul just used two if statements, I made a variable to hold a value of "0" and then inside the for loop I made another variable that held the expression "i * i" to later then use it, You get the idea I hope that I did "too much" was this wrong? What could I have changed in my code to make it better, without just simply copy pasting Paul's solution? Thank you for taking the time to read this, I look forward to your answers!

Some notes...

1. Check your bounds condition at the outset so you avoid doing any processing if it fails.
2. Your if powerOfTwoResult != i * i check will never pass, because right at the beginning of your loop, you explicitly set powerOfTwoResult = i * i
3. IMO, it's better to check if you have a match and return if you do, then if you make it all the way through the loop without matching anything, you can throw a noRoot error. But that's mostly a personal style thing, I think
4. Speaking of style, the Swift convention is to start type names with a capital letter, so SquareError instead of squareError. Following this convention will benefit you in the long run.

I see, Thank you both for your answers!