On Sunday, 14 June 2020 at 16:26:17 UTC, Avrina wrote:

The situation also applies to the only tuple implementation in D. If you are proposing a new type with emphasis on reducing the footprint of the tuple then I don't see a problem with that. Changing the existing tuple implementation would be problematic.

Presumably any such change would be made backwards-compatible. So Tuple.opIndex and Tuple.expand would still return elements in the order specified by the user, even if that order is different from the internal storage order.
  • Interesting work on packing... Andrei Alexandrescu via Digitalmars-d-announce
    • Re: Interesting work o... user1234 via Digitalmars-d-announce
    • Re: Interesting work o... Timon Gehr via Digitalmars-d-announce
      • Re: Interesting wo... Andrei Alexandrescu via Digitalmars-d-announce
        • Re: Interestin... Avrina via Digitalmars-d-announce
          • Re: Intere... Andrei Alexandrescu via Digitalmars-d-announce
            • Re: I... Avrina via Digitalmars-d-announce
              • R... Paul Backus via Digitalmars-d-announce
                • ... Timon Gehr via Digitalmars-d-announce
                • ... Andrei Alexandrescu via Digitalmars-d-announce
                • ... Max Samukha via Digitalmars-d-announce
                • ... Andrej Mitrovic via Digitalmars-d-announce
                • ... Max Samukha via Digitalmars-d-announce
                • ... Max Samukha via Digitalmars-d-announce
                • ... Timon Gehr via Digitalmars-d-announce
                • ... Andrej Mitrovic via Digitalmars-d-announce
                • ... Max Samukha via Digitalmars-d-announce
                • ... Andrej Mitrovic via Digitalmars-d-announce

Reply via email to