Using panic and recover is strongly discouraged, and in the rare cases where it makes the code significantly simpler, panics should never cross package boundaries (which is to say, you should never have a public API that can panic, unless you fully expect the panic to take down the process).
Using panics for control flow or having panics cross library boundaries is strongly discouraged, otherwise they are fine. Go's own standard library uses them internally in several places.
Even then discouraging panics is very different from not having them.
So if I'm reading from a file I should use panic recover and not return code checking?? That's not what I've seen in the docs.
Go does exception handling with panic, recover and its reflection syntax.