Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <160205083708.ZM29641@torch.brasslantern.com>
References: <CAKc7PVDKxBdZ+9teFDS+Zd3VCvr_JYTpiGtYNuyRicAUfPa4KA@mail.gmail.com>
 <160205083708.ZM29641@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Fri, 5 Feb 2016 18:24:20 +0100
Message-ID: <CAKc7PVBeEpTN9jTg9HQE_ycuOP+jFGEFQZ4hoz8oT8LRDogcYg@mail.gmail.com>
Subject: Re: Compiled files ignore aliases
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

Yes I thought about it and it's reasonable, though unsymmetrical. Zwc
changes things, there isn't full symmetry when sourcing file already
parsed or not, but see *. The "reasonable" is that parsing probably
does lookup each word in a hash table to see if there is an alias for
it. Compiling means skipping that time consuming process. So compiling
is maybe all or maybe mostly about ability of ignoring aliases. In my
project I'm being close to able to fully switch to function shadowing,
the only juggling is about compdef which isn't builtin, but that's too
handable by function shadowing (will have to wrap function by
function). Plugin architecture may be simply extended by constraint
"expect no aliases" and that's all, it's a luck that (*) plugin isn't
"a file to source", it's a software package which may have
constraints.

Best regards,
Sebastian Gniazdowski