From: Sebastian Gniazdowski <psprint@zdharma.org>
To: zsh-workers@zsh.org
Subject: Any chances "autoload -w digest.zwc" can be faster?
Date: Tue, 4 Jul 2017 17:12:31 +0200 [thread overview]
Message-ID: <etPan.595bb05f.38f57532.4e4d@zdharma.org> (raw)
Hello
I extract functions from .plugin.zsh files, then compile them as digest: zcompile -Uz lexicon.zwc functions/*
Checked that this line:
autoload -w ~/.zplugin/lexicon.zwc
takes 0.12 ms – less than a millisecond. But overall time of "zsh -i -c exit" doesn't change – is 250 ms.
The function extraction is pretty cool, (z) flag guarantees correct extraction. So I can do autoload of functions for lazy authors, not using autoload, defining functions in the sourced file (plugin.zsh).
This is cool but performance gain is expected from this. Any chances loading functions from digest can be optimized?
--
Sebastian Gniazdowski
psprint /at/ zdharma.org
reply other threads:[~2017-07-04 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=etPan.595bb05f.38f57532.4e4d@zdharma.org \
--to=psprint@zdharma.org \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).