←back to thread

612 points dayanruben | 1 comments | | HN request time: 0s | source
Show context
alain_gilbert ◴[] No.42901749[source]
Swift is a really cool language.

But one thing that blows my mind is that if you ever encounter an "index out of range" error, the (massive) error message that you get doesn't tell you anything about where this error occurred... no line number... no nothing...

    let a = [1]
    print(a[1])
Is all you have to do to reproduce the error.

The error looks something like that https://pastebin.com/MQV82SaR

And gives you no useful information as to how it happened or how to fix it.

compare that with Golang which tells you, it happened in main.go at line 4.

    panic: runtime error: index out of range [1] with length 1
    
    goroutine 1 [running]:
    main.main()
     /Users/username/main.go:4 +0x15
    exit status 2
EDIT: with the LLVM_SYMBOLIZER_PATH set https://pastebin.com/8M9Dbrgj this doesn't provide anything useful either.
replies(8): >>42901838 #>>42901880 #>>42901928 #>>42903264 #>>42903913 #>>42906968 #>>42907652 #>>42944126 #
mojuba ◴[] No.42901838[source]
You have a stack dump, which means you will get all the information if you symbolicate your crash report. Xcode can do it for you automatically, but some manual methods also exist.
replies(1): >>42901964 #
robotresearcher ◴[] No.42901964[source]
Indeed the error report being complained about explains this and tells you how to fix it.

Maybe the friendly default would be to have the symbolicated reports on, but perhaps this has performance impact so it’s off.

replies(2): >>42902221 #>>42902925 #
1. ◴[] No.42902925{3}[source]