From: Thomas Rast <trast@inf.ethz.ch>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: <git@vger.kernel.org>
Subject: Re: [RFC] speed up git submodule
Date: Mon, 17 Jun 2013 10:29:44 +0200 [thread overview]
Message-ID: <87a9mpgmx3.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <1371427503-9678-1-git-send-email-iveqy@iveqy.com> (Fredrik Gustafsson's message of "Mon, 17 Jun 2013 02:05:03 +0200")
Fredrik Gustafsson <iveqy@iveqy.com> writes:
> The interesting feature would be to run C-functions direct inside lua. I
> suppose that would increase speed even more, at the same time as we have
> the convinence of a interpreted language. Lua is smaller and faster
> (well as always, it depends on what you're doing) than python and ruby.
> Perl is a really pain for the windows folks (I've heard).
>
> A correct implementation for lua support would be to start a
> lua-interpreter from inside git.c (or somewhere) and load the lua code
> for a specific command. That would make us independent of any target
> installation of lua (althought the git binary would increase with the
> lua library around 300 kb).
>
> However I did a quick test using lua as a replacement for sh (without
> direct calls to c-functions) and the result is impressive. (However this
> is the wrong way of using lua, shell scripting is not something lua is
> good at).
Ok, so as you say, to really buy us anything you'd have to interface lua
with the C code directly. Otherwise you might as well write it in Perl
instead which is already a requirement for a lot of the "niceties".
However, instead of writing against git's C code, you could also
interface with libgit2, either from Lua or Perl...
BTW Peff once posted an interface to Lua for the --pretty formatters:
http://thread.gmane.org/gmane.comp.version-control.git/206335
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2013-06-17 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 0:05 [RFC] speed up git submodule Fredrik Gustafsson
2013-06-17 8:29 ` Thomas Rast [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9mpgmx3.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
/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://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).