[swift-evolution] [Review] SE-0026 Abstract classes and methods

[Howard Lovatt]

At least it isn't the Miley Cyrus:

“Miley Cyrus - Wrecking Ball (Explicit Video)”

  -- Howard.

On 10 March 2016 at 14:50, Erica Sadun via swift-evolution <
swift-evolution at swift.org> wrote:

>
> On Mar 9, 2016, at 8:46 PM, Chris Lattner via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>
> On Mar 9, 2016, at 12:35 PM, Evan Maloney via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> On Mar 4, 2016, at 5:42 AM, Haravikk via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> Someone asked in this discussion whether classes are second-class citizens
> in Swift, and thinking about it some more I kind of think that they are;
> after a period of adjustment I now use structs for almost everything. I
> only use classes where a common reference is absolutely necessary, and also
> for nested types.
>
>
> It seems to me that you are using classes and structs in exactly the right
> way. However, I don't think your judicious use of classes is necessarily an
> argument that "classes are second-class citizens in Swift".
>
> Sometimes classes are the right tool for the job. Sometimes structs or
> enums are.
>
> What I love about Swift is that it's often much easier to use the right
> tool for the right job than other languages. However, if classes are
> relegated to some sort of demoted status, over time, that would no longer
> be the case.
>
>
> +1.  Swift loves OOP as well as POP (not to mention FP).  They are both
> complementary techniques which are great at solving certain kinds of
> problems.
>
> -Chris
>
>
> Swift is the Hannah Montana of programming languages.
> https://www.youtube.com/watch?v=uVjRe8QXFHY
>
> -- E, a mommy
>
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160310/b9ee591b/attachment.html>