From: ron minnich <rminnich@gmail.com>
To: Raghavan Raman <ragr@uber.com>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Coccinelle for Go
Date: Sun, 21 Jul 2019 22:04:06 -0700 [thread overview]
Message-ID: <CAP6exYLjntc0iPNOHdWSSUMw-ay3n4dFBAFfW=6Y1SOvmXT-Gg@mail.gmail.com> (raw)
In-Reply-To: <CAEgVsn4+aMn_3pXo1fex6_3oWmHbQERhmr42dO0igdFT1u67nA@mail.gmail.com>
Given the existence of the go AST package, which is used in so many
ways to rewrite Go code (gofmt and go imports to name just two), I'm
not sure I see the
need for coccinelle. This is not in any way a criticism of coccinelle,
I use it all the time for C. But I also write tools that
use the Go AST package to rewrite Go, and have never felt the lack of
coccinelle for Go. I'm curious what you see as the use case.
ron
On Sat, Jul 20, 2019 at 2:55 AM Raghavan Raman <ragr@uber.com> wrote:
>
> Hi,
>
> I am part of the Programming Systems group at Uber. We are looking into using Coccinelle for refactoring in Go.
>
> Does Coccinelle include support for Go?
>
> If not:
> * Is there any plan to add support for the same?
> * What would it take to add this support? Any documentation regarding this?
>
> Thanks,
> Raghavan
>
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-07-22 5:04 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 [this message]
2019-07-22 6:00 ` Markus Elfring
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='CAP6exYLjntc0iPNOHdWSSUMw-ay3n4dFBAFfW=6Y1SOvmXT-Gg@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=cocci@systeme.lip6.fr \
--cc=ragr@uber.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).