From: Markus Elfring <Markus.Elfring@web.de>
To: Ron Minnich <rminnich@gmail.com>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Coccinelle for Go
Date: Mon, 22 Jul 2019 08:00:17 +0200 [thread overview]
Message-ID: <97b1adc6-b176-bc37-7224-aee45ff073d7@web.de> (raw)
In-Reply-To: <CAP6exYLjntc0iPNOHdWSSUMw-ay3n4dFBAFfW=6Y1SOvmXT-Gg@mail.gmail.com>
> But I also write tools that
use the Go AST package to rewrite Go,
Would you like to share any more experiences around related software?
> and have never felt the lack of
coccinelle for Go.
I find this impression interesting.
How much did you get used to functionality which is supported by
the semantic patch language?
> I'm curious what you see as the use case.
Are you looking for wider support of a known programming interface?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2019-07-22 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 7:34 [Cocci] Coccinelle for Go Raghavan Raman
2019-07-21 11:45 ` Markus Elfring
2019-07-24 22:24 ` Raghavan Raman
2019-07-22 5:04 ` ron minnich
2019-07-22 6:00 ` Markus Elfring [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97b1adc6-b176-bc37-7224-aee45ff073d7@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=rminnich@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.
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).