Removing braces for scope would cause more problems than whatever you would 
gain from it - it is one character at the end of a function declaration and one 
at the end of a function.

Using white space to (indentation sometimes is a tab, sometimes and sometimes 
get mixed up) scope is not the best way to do it.  

-1


> On 2015-12-20, at 8:58:02, Kevin Ballard via swift-evolution 
> <[email protected]> wrote:
> 
> There is not in fact an emphasis on conciseness. This has been repeated many 
> times by the swift team. Conciseness is not a goal of Swift, but 
> expressiveness absolutely is. Braces are a well-understood and simple way to 
> express the notion of a scope/closure. And FWIW removing braces means you 
> have to come up with a completely different syntax for closures, because 
> indentation does not suffice there.
> 
> Also, "don't be like C" is not even remotely a goal of Swift. The Swift 
> syntax is C-like in many respects. "Be like C" isn't a goal either of course, 
> but when deciding between two alternatives that have no compelling arguments 
> either way, picking the one that would be more familiar to Obj-C programmers 
> is usually a good idea.
> 
> -Kevin Ballard
> 
> On Sat, Dec 19, 2015, at 05:39 PM, Alexander Regueiro via swift-evolution 
> wrote:
>> Has anyone considered removing braces from the Swift language? The main 
>> alternative would be indentation-based scoping like in Python or Ruby. There 
>> already seems to be a general emphasis on conciseness,  lack of redundancy, 
>> and a modern syntax. e.g. semicolons are not required for single-line 
>> statements; brackets have been removed from if/for/while expressions, 
>> compared to C-style syntax. So, why not go the whole way in breaking the 
>> C-style connection? The present syntax seems to be shunning C, but only 
>> slightly.
>> 
>> Thoughts?
>> _______________________________________________
>> 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

_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to