Type inference sounds nice initially then you face the costs in compilation time and reduced ability to debug and reason about the code months after the fact... and you start to rethink things (not every programmer keeps maintainability over pretty smart haiku code).
Sent from my iPhone > On 8 Apr 2017, at 07:35, David Sweeris via swift-evolution > <[email protected]> wrote: > > >> On Apr 7, 2017, at 22:40, Pranshu Goyal via swift-evolution >> <[email protected]> wrote: >> >> I agree with the sentiment of the proposal, it does add value to overall >> efficiency of swift and make things simpler for the swift team, but as >> Matthew said a blanket ban will add noise to the code. Also this particular >> feature is one of those niceties about swift which makes it very welcoming >> to new adopters. >> >> If some middle ground can be proposed to this problem then I think we will >> be making a lot of people happy. > > I don't think I'd mind a flag that disables type inference for properties or > something. Really, though, this seems like a linter's job to me. > > Maybe the Swift manual should have a chapter about the trade-offs between > code that's quick to write, quick to run, and quick to compile? > > - Dave Sweeris > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
