From: Markus Elfring <Markus.Elfring@web.de>
To: Raghavan Raman <ragr@uber.com>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Coccinelle for Go
Date: Sun, 21 Jul 2019 13:45:31 +0200 [thread overview]
Message-ID: <8d566cd5-d693-1d66-3f14-e3a6291f7922@web.de> (raw)
In-Reply-To: <CAEgVsn4+aMn_3pXo1fex6_3oWmHbQERhmr42dO0igdFT1u67nA@mail.gmail.com>
> We are looking into
using Coccinelle for refactoring in Go
Thanks for your interest.
> Does Coccinelle include support for Go?
Not yet.
> * Is there any plan to add support for the same?
Would you like to contribute significant development resources for
corresponding software extensions?
> * What would it take to add this support?
Remarkable desire for collateral evolution.
> Any documentation regarding
this?
Yes, of course.
Did you notice information sources like the following already?
* Paper “Computation tree logic with variables and witnesses”
http://coccinelle.lip6.fr/papers/popl09.pdf
https://doi.org/10.1145/1480881.1480897
* Manual for the semantic patch language
https://github.com/coccinelle/coccinelle/blob/ed1eb8e06f800739d3992158d36945c0c4c6f0c7/docs/manual/cocci_syntax.tex#L50
* Clarification request: Support for more programming languages?
https://systeme.lip6.fr/pipermail/cocci/2016-July/003445.html
https://lore.kernel.org/cocci/76bf1017-d629-d44a-5493-0dcccbbfa65b@users.sourceforge.net/
How do you think about to improve related technologies?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-07-21 11:46 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 [this message]
2019-07-24 22:24 ` Raghavan Raman
2019-07-22 5:04 ` ron minnich
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=8d566cd5-d693-1d66-3f14-e3a6291f7922@web.de \
--to=markus.elfring@web.de \
--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).