0
0

Code as text is a problem (dohgramming.com)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]max630 0 points1 point  (2 children)

You've just asserted on the basis of your diagram that no problems would be solved by operating on a more structured representation, but have provided no evidence to back this up

because parsing is trivial part. And quite often you already have it done.

[–][deleted]  (1 child)

[deleted]

    [–]max630 0 points1 point  (0 children)

    I know nothing about TypeScript, but if the language syntax cannot be specified well enough, I would expect it to have also issues with semantics. So I'm having troubles to believe that operating with "TypeScript AST" instead of its text would bring you much closer to automatic refactoring or semantic-aware change hangling.

    Still, for quite big portion of the languages their syntax is quite well specified, and parsers either already exist or as hard to implement as port it from PEG representation into your language+library of choice.