From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2439 invoked by alias); 4 Mar 2017 17:29:03 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40723 Received: (qmail 8276 invoked from network); 4 Mar 2017 17:29:03 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk0-f53.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.213.53):SA:0(-0.0/5.0):. Processed in 1.898413 secs); 04 Mar 2017 17:29:03 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.213.53 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=HDENHmEC66hy59izlJSMRpbr/QrmyvSmeEka2mrqTKE=; b=AOE6D3OQAvpwODBBlDlTbXAy8u9eTdnSG+j5GMEafZYQuZvF6oh2su5c8s4sOk8G45 Hk0fRE7E0L5SouJbvIwpXPzX8VH89Fu8Amj+J5BtLOb2khJEWpxPRSdYYp/k1zscD5ar AJVGXZvqhTQrbsspYHhcBXTl82Ze5iVtk3aK7va7kcGHKzJMK80JBstHpNUgMC+/VRF5 JH7O0qMC2bI+CS0DBretxtGu7DJOTXazldFkFOE4WJkDRXnJwS4J/kUE74daSzj9peTM iePf/IzfEP1FcFqvJ+SLh1sgC+YF5zFTe0M48yFdJjicToqfudBynqY3ZJfEn9kfj24S nJwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=HDENHmEC66hy59izlJSMRpbr/QrmyvSmeEka2mrqTKE=; b=GGTZrJeHA0V9zKqnU5V6nA9qwGlcSZJNUrghDW3c8hF/Z3RIYhGX79IE1P0CKZZB3J 3KMzBCSmEEV7IIm8pn4lGX995oQdOxgrpN5acaxYr5GQz1Pfd1ecG3/mTI/9ailBCRdu PtBxZyt4701jIWQS+i9HXKQc1Zbae9RkHecbzPQe/IQ6gHnCCaj/Y5r1WJAyoTBIhEJ3 JCXnRMpUpQ/NphnBgELbr1ldqvq4jxjxVHt8JtZfGLtEPZ3EqMLrFRRuJTa28lGpwVpt ygUbybZN5F75j0Gl01iwbPnyWDBceawgc0Ac+wERwesqPuzV+l9C7JlPMeOIPANJtu+I HRog== X-Gm-Message-State: AMke39m1gRXz4giehV7mknXU6LozlhFxRRVSz4+ICZ8QKv93G7F8RoXQZJQrcWe0amPTTw== X-Received: by 10.31.208.133 with SMTP id h127mr3641317vkg.96.1488648125743; Sat, 04 Mar 2017 09:22:05 -0800 (PST) From: Bart Schaefer Message-Id: <170304092226.ZM23592@torch.brasslantern.com> Date: Sat, 4 Mar 2017 09:22:26 -0800 In-Reply-To: <1488635259.1730344.900251328.5D6F1325@webmail.messagingengine.com> Comments: In reply to Sebastian Gniazdowski "Re: [PATCH] zrealloc on array+=( )" (Mar 4, 5:47am) References: <1488635259.1730344.900251328.5D6F1325@webmail.messagingengine.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: [PATCH] zrealloc on array+=( ) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 4, 5:47am, Sebastian Gniazdowski wrote: } } I revisited the patch, tested with debug prints, added test cases that } stress things out. No code changes. For the record, this looks fine, I don't see any reason not to pick it up. } We can leverage the fact that operating system has size of the array } and can extend it, and this way beat Bash. IIRC bash implements arrays sparsely as linked lists, so is going to differ entirely from zsh in memory-use/execution-speed profile for various array operations. "Beating" bash on some specific usage is not especially meaningful. } Of course, the real deal here is to be able to do } data processing, e.g. log gathering, etc. Which is not really what shells are intended to be used for ...