From: Junio C Hamano <gitster@pobox.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC][PATCH v3 1/1] userdiff: add support for Scheme
Date: Mon, 12 Apr 2021 16:04:04 -0700 [thread overview]
Message-ID: <xmqqzgy39kbf.fsf@gitster.g> (raw)
In-Reply-To: <20210408091442.22740-2-raykar.ath@gmail.com> (Atharva Raykar's message of "Thu, 8 Apr 2021 14:44:43 +0530")
Atharva Raykar <raykar.ath@gmail.com> writes:
> Add a diff driver for Scheme-like languages which recognizes top level
> and local `define` forms, whether it is a function definition, binding,
> syntax definition or a user-defined `define-xyzzy` form.
>
> Also supports R6RS `library` forms, `module` forms along with class and
> struct declarations used in Racket (PLT Scheme).
>
> Alternate "def" syntax such as those in Gerbil Scheme are also
> supported, like defstruct, defsyntax and so on.
>
> The rationale for picking `define` forms for the hunk headers is because
> it is usually the only significant form for defining the structure of
> the program, and it is a common pattern for schemers to have local
> function definitions to hide their visibility, so it is not only the top
> level `define`'s that are of interest. Schemers also extend the language
> with macros to provide their own define forms (for example, something
> like a `define-test-suite`) which is also captured in the hunk header.
>
> Since it is common practice to extend syntax with variants of a form
> like `module+`, `class*` etc, those have been supported as well.
>
> The word regex is a best-effort attempt to conform to R7RS[1] valid
> identifiers, symbols and numbers.
>
> [1] https://small.r7rs.org/attachment/r7rs.pdf (section 2.1)
>
> Signed-off-by: Atharva Raykar <raykar.ath@gmail.com>
> ---
> Documentation/gitattributes.txt | 2 ++
> t/t4018-diff-funcname.sh | 1 +
> t/t4018/scheme-class | 7 +++++++
> t/t4018/scheme-def | 4 ++++
> t/t4018/scheme-def-variant | 4 ++++
> t/t4018/scheme-define-slash-public | 7 +++++++
> t/t4018/scheme-define-syntax | 8 ++++++++
> t/t4018/scheme-define-variant | 4 ++++
> t/t4018/scheme-library | 11 +++++++++++
> t/t4018/scheme-local-define | 4 ++++
> t/t4018/scheme-module | 6 ++++++
> t/t4018/scheme-top-level-define | 4 ++++
> t/t4018/scheme-user-defined-define | 6 ++++++
> t/t4034-diff-words.sh | 1 +
> t/t4034/scheme/expect | 11 +++++++++++
> t/t4034/scheme/post | 6 ++++++
> t/t4034/scheme/pre | 6 ++++++
> userdiff.c | 9 +++++++++
> 18 files changed, 101 insertions(+)
> create mode 100644 t/t4018/scheme-class
> create mode 100644 t/t4018/scheme-def
> create mode 100644 t/t4018/scheme-def-variant
> create mode 100644 t/t4018/scheme-define-slash-public
> create mode 100644 t/t4018/scheme-define-syntax
> create mode 100644 t/t4018/scheme-define-variant
> create mode 100644 t/t4018/scheme-library
> create mode 100644 t/t4018/scheme-local-define
> create mode 100644 t/t4018/scheme-module
> create mode 100644 t/t4018/scheme-top-level-define
> create mode 100644 t/t4018/scheme-user-defined-define
> create mode 100644 t/t4034/scheme/expect
> create mode 100644 t/t4034/scheme/post
> create mode 100644 t/t4034/scheme/pre
We have seen reviews on previous rounds, and haven't heard anything
on this round yet.
If I do not hear from anybody in a few days, let's merge it to
'next'.
prev parent reply other threads:[~2021-04-12 23:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 17:39 [GSOC][PATCH] userdiff: add support for Scheme Atharva Raykar
2021-03-27 22:50 ` Junio C Hamano
2021-03-27 23:09 ` Junio C Hamano
2021-03-28 3:16 ` Ævar Arnfjörð Bjarmason
2021-03-28 5:37 ` Junio C Hamano
2021-03-28 12:40 ` Atharva Raykar
2021-03-29 10:08 ` Phillip Wood
2021-03-30 6:41 ` Atharva Raykar
2021-03-30 12:56 ` Ævar Arnfjörð Bjarmason
2021-03-30 13:48 ` Atharva Raykar
2021-03-28 12:45 ` Atharva Raykar
2021-03-28 11:51 ` Atharva Raykar
2021-03-28 18:06 ` Junio C Hamano
2021-03-29 8:12 ` Atharva Raykar
2021-03-29 20:47 ` Junio C Hamano
2021-03-29 10:12 ` Phillip Wood
2021-03-27 23:46 ` Johannes Sixt
2021-03-28 12:23 ` Atharva Raykar
2021-03-29 10:18 ` Phillip Wood
2021-03-29 10:48 ` Johannes Sixt
2021-03-29 13:12 ` Ævar Arnfjörð Bjarmason
2021-03-29 14:06 ` Phillip Wood
2021-03-30 7:04 ` Atharva Raykar
2021-03-30 10:22 ` Atharva Raykar
2021-04-05 10:04 ` Phillip Wood
2021-04-05 17:58 ` Johannes Sixt
2021-04-06 12:29 ` Atharva Raykar
2021-04-06 19:10 ` Phillip Wood
2021-04-03 13:16 ` [GSoC][PATCH v2 0/1] userdiff: add support for scheme Atharva Raykar
2021-04-03 13:16 ` [GSoC][PATCH v2 1/1] " Atharva Raykar
2021-04-05 10:21 ` Phillip Wood
2021-04-06 10:32 ` Atharva Raykar
2021-04-08 9:14 ` [GSoC][PATCH v3 0/1] " Atharva Raykar
2021-04-08 9:14 ` [GSoC][PATCH v3 1/1] userdiff: add support for Scheme Atharva Raykar
2021-04-12 23:04 ` Junio C Hamano [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=xmqqzgy39kbf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=raykar.ath@gmail.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).