3 ms·
The curious case of the broken inverse: you won't get more type safety by having type inference, but you are likely to end up with less type safety when you are
by usrusr 11y ago
The curious case of the broken inverse: you won't get more type safety by having type inference, but you are likely to end up with less type safety when you are not having it ;)
- incepted 11y agoI have seen no evidence of that. With that logic, Java programmers would use "Object" instead of "List<String>" because they have fewer characters to type? This makes no sense.
- usrusr 11y agoIt makes more sense after you have deliberately weakened the typing of an API because you felt that you were overstretching your co-developers (and/or your own) patience for nested angle brackets. The basic idea is that type inference would shift the sweet spot for the right amount of typing upwards.