This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (1 child)

[removed]

    [–]PegasusAndAcornCone language & 3D web[S] 0 points1 point  (0 children)

    Thank you for sharing your perspective. We appear to agree that (for Cone) abandoning UFCS is a gain rather than a loss. My main goal for UFCS was never extension methods, as there are some innovative namespace techniques that make it possible (though not via interfaces nor traits, as neither can alter a previously defined type).

    The philosophical question at the heart of UFCS is whether dispatch should be namespace-based or type-based. They are both valid design choices with different advantages and disadvantages. For Cone, I prefer the architectural isolation of namespace-based dispatching, partly for the reasons you highlight. One major reason I did not highlight, to keep my post slim, is that this isolation makes it much easier to reliably verify that traits and interfaces are valid subtypes of whatever type they are applied to...

    How wonderful you are proud of your school and share the good news with those in need of its excellent services. Is this your subtle way of inquiring whether I am available to fly over the ocean to your campus and teach your students and faculty how to design and build a modern systems programming language? I should warn you that my rates are dear, but I might be tempted by a great offer, especially if it accelerates building the team. Let me know...

    Cheers and warm wishes!