3 ms·
I thought the whole point of this approach, an option for a language/system to not check types in production, was for performance reasons. Is there another good
by 83457 15y ago
I thought the whole point of this approach, an option for a language/system to not check types in production, was for performance reasons. Is there another good reason, or might that be a typo in "type checks are not a major drain on performance"?
- munificent 15y agoMy understanding was that the prime original motivation for unchecked mode was indeed performance. As our Dart implementations are getting more mature, we're starting to get a better picture of how it does actually impact performance. I think what we're starting to see is that the performance implications aren't that bad. Given that, I think we're focusing less and less on production mode. It's still a valid option and it may make sense for some users but it may not be commonly used, sort of like -Ofast in gcc.