The entire article could basically be boiled down to your first sentence + the two code examples. And IMO the title is still inaccurate because it attacks a ge

The entire article could basically be boiled down to your first sentence + the two code examples. And IMO the title is still inaccurate because it attacks a general promised/desired property of Rust (and other languages) and I honestly don't see the connection. Looks like the observed behaviour is an unfortunate side effect of the `newtype` thing and is very prone to fixing and optimization in future versions. It's not a failure of the "zero-cost abstraction" ideal which is being chased after every day and is still in flux.