The first one (string with variable interpolation) is not internationalizable, only the third one is. > the third has ordering issues In Go you can specify the order in format strings: fmt.Sprintf("%[2]d %[1]d\n", 11,…
That's a strange definition of "crash" you have there. I should go tell my customers next time that their programs definitely didn't crash.
Yes, I can catch SIGSEGV. And I can catch Java NullPointerExceptions and ArrayIndexOutOfBoundsExceptions. So Java prevents all crashes, lol.
This prevents buffer overflow errors, but not crashes.
> it will cause a task failure i.e. a crash.
From the project home page: "prevents almost all crashes (in theory)" How does it prevent index out of bounds errors and division by zero? No, not even in theory. What a ridiculous claim.
The first one (string with variable interpolation) is not internationalizable, only the third one is. > the third has ordering issues In Go you can specify the order in format strings: fmt.Sprintf("%[2]d %[1]d\n", 11,…
That's a strange definition of "crash" you have there. I should go tell my customers next time that their programs definitely didn't crash.
Yes, I can catch SIGSEGV. And I can catch Java NullPointerExceptions and ArrayIndexOutOfBoundsExceptions. So Java prevents all crashes, lol.
This prevents buffer overflow errors, but not crashes.
> it will cause a task failure i.e. a crash.
From the project home page: "prevents almost all crashes (in theory)" How does it prevent index out of bounds errors and division by zero? No, not even in theory. What a ridiculous claim.