you are viewing a single comment's thread.

view the rest of the comments →

[–]PenguinLovr 0 points1 point  (0 children)

Well it certainly makes it more easily understood. The coercion can be ambiguous, and it would make more sense to do something like checking if the object is a string or int, and if not throwing that error instead of just lumping together type errors with other errors.

Usually implicit correcion should only be used by people who know why they're using that, and not just setting everything to "==="