For 1. I disagree with you, I consider it perfectly elixiry. The function is for data that you know can be parsed as an integer. You should not use it for unknown inputs. The documentation is pretty clear
stringmust be the string representation of an integer. Otherwise, anArgumentErrorwill be raised. If you want to parse a string that may contain an ill-formatted integer, useInteger.parse/1.
What makes Integer.parse explode? It should give you either a tuple of number and remainder or :error.
Ah, I see it raises if you give it an invalid base, not because you give it an invalid string input.






















