-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PROPOSAL] Source code transformations #241
Comments
Hey Alex, maybe I'm lacking knowledge here but the title doesn't mean anything to me. |
Thank you for feedback, Francesc! It's totally WIP as I'm just gaining confidence in existing tools in this field. The plan is basically to cover some "state of the art" tools for AST transformation (AKA refactoring), so the learnings could be applied to Bblfsh UAST manipulation API. How about the title along the lines of "Source code transformations"? OSS:
Proprietary/from talks or papers (material)
|
Source code transformations makes it much more clear to me, yeah. I'd be curious to see if we can make it so the blog doesn't feel like a series of tools, and instead there's a story tying everything up. |
that is very useful feedback, thank you and please let me think more about that. Thanks again. |
@campoy One story I can think of is: take simple-but-educational example(s) of some issue in the code as a motivation, and then go though implementing:
Due to differences in host languages it could be hard to pick a single example, so it can be adjusted a bit for each specific language, keeping it sufficiently high-level. A Nice 🍒 on top could be finishing it with the link to a blog post on "how to wrap it as a lookout analyzer" from #249 . WDYT? |
I like it, even if we find an example that only works for a specific language it should be easy to get people from other language communities understand the point of the article. |
Refactoring prolog code: https://pdfs.semanticscholar.org/b48b/bc30427ef7429db83e190f91a579442121b6.pdf |
@bzz did you get a chance to start a draft ? |
Very preliminary - this is fairly ambitious and requires a lot of research. I would expect a shareble draft early next year. |
@bzz Trying to plan our blog schedule for the upcoming weeks. Did you get a chance to work on this draft ? |
@vcoisne did some progress on research but not there yet. |
This is still in my backlog. Two more interesting contenders added to the description:
|
Idea comes from #233 (comment)
Table of contents
Very rough grounds that would be covered
OSS:
Proprietary/from talks or papers (material)
details section below
)with some basic examples of using each API, and conclusion why bblfsh is the best tool for us.
Management
This section will be filled by @campoy.
Social Media
NOTE Please write in short lines so the review is easier to do.
Preliminary content comes from prev. blog pos
The text was updated successfully, but these errors were encountered: