[swift-evolution] Make non-void functions @warn_unused_result by default
Gwendal Roué
gwendal.roue at gmail.com
Wed Feb 24 16:47:52 CST 2016
Oh yes please, don't rush on this...
Who do we want to help here? API users, or API developers?
Considering that Swift may be on the verge of a great breakthrough, plenty of immature yet popular libraries will ship. Plenty have already shipped. This is a great sign of vitality. Should @warn_unused_result become the default, the quality of the code of the users of those libraries risks a brutal degradation, full of poor `let _ = ...`.
Gwendal
> Le 24 févr. 2016 à 16:01, Jean-Daniel Dupas via swift-evolution <swift-evolution at swift.org> a écrit :
>
> IMHO, before any decision, it may be interesting to write a quick patch and run the modified compiler on real code to see how much false positive it would generate.
>
>> Le 24 févr. 2016 à 16:13, Janosch Hildebrand via swift-evolution <swift-evolution at swift.org> a écrit :
>>
>> Erica's proposal about "Modernizing Attribute Case and Attribute Argument Naming" made me remember this discussion.
>>
>> I don't think a proposal was ever submitted? If no one else is working on a proposal already I would offer myself up for writing this up.
>>
>> - Janosch
>>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
More information about the swift-evolution
mailing list