From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Josh Holland <anowlcalledjosh@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] userdiff: support Python async functions
Date: Tue, 12 Nov 2019 13:43:10 +0900 [thread overview]
Message-ID: <xmqqtv79g0wx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <f8a729c6-7b27-cac8-815e-b5c02a5c7b44@kdbg.org> (Johannes Sixt's message of "Mon, 11 Nov 2019 18:27:24 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
>> ...
>> @@ -0,0 +1,4 @@
>> +def RIGHT(pi: int = 3.14):
>> + while True:
>> + break
>> + return ChangeMe()
>
> Thank you for providing test cases for Python.
>
> I have one gripe with this set of test, though: They do not demonstrate
> that the Python-specific pattern is better than the default pattern. In
> fact, if you remove the Python patterns from userdiff.c, you will
> observe that these tests still pass.
>
> The one thing that the language specific pattern would do better than
> the default is that it picks up indented text. Could we have a test case
> or two that show that it indeed does?
Good point. A method "def" inside a "class" would be one level
indented; I am not sure if it is a kosher style to have "if" at the
unindented top-level, whose body conditionally defines a "class",
but such a class definition would also be indented, I guess.
Thanks.
prev parent reply other threads:[~2019-11-12 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 1:01 [PATCH] userdiff: support Python async functions Josh Holland
2019-11-11 2:28 ` Junio C Hamano
2019-11-11 17:27 ` Johannes Sixt
2019-11-12 4:43 ` 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=xmqqtv79g0wx.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=anowlcalledjosh@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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://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).