> On Aug 25, 2017, at 2:34 AM, Slava Pestov <spes...@apple.com> wrote: >> On Aug 24, 2017, at 10:56 PM, John McCall via swift-dev <swift-dev@swift.org >> <mailto:swift-dev@swift.org>> wrote: >> >> Or if you really want to avoid the FFI, you could take our current ASTDumper >> output, which is currently pseudo-machine-readable, and make it actually >> machine-readable. The elegant approach there would be to take the entire >> dumper and remove its pervasive dependence on an output stream; instead, it >> would be rewritten to make calls on a SAX-like streaming interface, and >> there would just be a standard implementation that formatted things as XML / >> JSON / our weird s-expression format. > > … I would love it if ASTDumper supported a Clang-like tree view in addition > to (or instead of, if we also get JSON output?) the faux s-expression output. > I know I’m supposed to like Lisp, but I personally find our dump output > rather hard to read.
Yeah, it would be a great design goal that this output could be fed into various standard visualization tools. John.
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
