News for hackers. Stuff that matters.
Re:App Developers on Swift Evolution by hyperpape on Tuesday December 22, 2015 @11:31PM (#10781967)
I immediately agreed with what you wrote, but now there's a voice in the back of my head asking "if this is so obviously right, why is it just happening now, after 2.0? It's not like this Lattner guy doesn't know what method calls cost..."

A post last week featured Lattner writing about Swift treating methods as final when they weren't declared that way (https://lists.swift.org/pipermail/swift-evolution/Week-of-Mo...). I wonder if the early thought was that they'd get enough mileage out of those "cheats", and then later decided that final should be the default.

Re:App Developers on Swift Evolution by pcwalton on Tuesday December 22, 2015 @11:50PM (#10782024)
Probably. It's hard to predict how language design decisions will impact performance (and everything else, such as ease of use and productivity). That's why it's good to have an iterative process (like Swift is now adopting) instead of being rigid, inflexible, and opinionated.