1. 7
  1.  

  2. 7

    The but operator has a brother: an infix does operator. It behaves very similarly, except it does not clone.

    Perl6 is like C++. They jumped the shark long ago: Both these languages have become so complex and arcane.

    For a language to work for me, I need to be able to grok the “base language” – hold the whole thing in my head. The complexity should reside in the libraries.

    1. 2

      I agree they both have a problem saying “no” to new features, but at least I understand the use cases for features that get tacked onto C++.

      Sometimes Perl6 seems like an elaborate troll or esoteric joke language.

      1. 1

        In terms of grokking “the language”, there is not much difference between a language feature and a library. If the library is out of your problem domain, you can ignore it; if the language feature feels arcane, you can ignore it, too. I know some C++ projects that have rules allowing only a strict set of template features. So be it. You won’t need to know anything about SFINAE to work productively in those projects.

        1. 5

          Right up until you are trying to debug a problem happening in an upstream library that you don’t control.

      2. 1

        I can’t help but wonder at having does-added methods which override the self-same method and using this to implement a state machine.