[swift-evolution] Beyond Typewriter-Styled Code in Swift, Adoption of Symbols

David Sweeris davesweeris at mac.com
Thu Aug 31 16:58:57 CDT 2017

> On Aug 31, 2017, at 2:51 PM, Dave DeLong via swift-evolution <swift-evolution at swift.org> wrote:
> Just a side observation…
> One of the downsides I would put forward to notation like this is it massively increases the barrier to entry for anyone else. I look at that “Reduction.agda” file and wonder if I need to go back to school for a degree in Math just to understand what’s going on.
> On the other hand, while using inefficient matrix notation may be more verbose, it is consistent with the other notation used in programming, which means it is more easily understandable for new-comers to the code.

New-comers from where? I've met more than one mathematician or physicist who claims they can't code because the syntax isn't what they're used to. People with different backgrounds can and do have vastly different ideas about what constitutes an intuitive syntax for any given semantic (which why I disagree with the notion that having more than one spelling for stuff is inherently bad).

- Dave Sweeris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170831/9f04601c/attachment.html>

More information about the swift-evolution mailing list