GSoC Swift compiler integration with external tools

[Kazutaka333 (Kazutaka Homma)]

Thank you @rintaro!

@rintaro

Receive a libSyntax tree and compiler arguments form, via STDIN using JSON format
Return diagnostics via STDOUT using JSON format

I got it. Thank you!

@rintaro

Also, external tools should be able to be written in Swift. So I expect you to design/implement a Swift framework using SwiftSyntax.

This swift framework that I'm expected to implement is for reconstructing libSyntax tree from JSON format and what else does it need to do?

I was also looking at another post by you [1]

@rintaro

We already have a serializer; try swift -frontend -emit-syntax source.swift with the latest master build. For the deserializer, we are able to use LLVM YAML parser.

From this, I assumed I used the same seializer and deserializer for my task. is that correct?

To be accurate, the current Parser generates both AST and libSyntax tree. But I guess it’s difficult to use the current libSyntax tree generation functionality for this task. Currently, it’s like a by-product of AST parsing.
This means his task would change the libSyntax to be generaeted

Should I worry about how the libSyntax tree output would change due to his change?

[1] [GSOC]Integration of libSyntax with the rest of the compiler pipeline - #4 by rintaro