<div dir="ltr">I would not recommend phrasing these proposals as "Why doesn't Swift already support X?" when you are proposing a new feature.<div><br></div><div>Instead, I'd like to see much more fleshed out examples of what you'd propose to change, and how it would help Swift developers. From the small amount of information you've given here, I can't understand what you're trying to do.<div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>Jacob</div></div></div></div>
<br><div class="gmail_quote">On Tue, Dec 29, 2015 at 10:07 AM, Amir Michail via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Source to source transformations are part of a developer’s job, don’t need a GUI, and can be done more easily and accurately by the Swift compiler. Moreover, the compiler could be made interactive taking in extra information from the developer as required during the "compile" (again without requiring a GUI).<br>
<br>
You could have special directives for source to source transformations such as:<br>
<br>
@extractMethodBegin<br>
… swift code ...<br>
@extractMethodEnd<br>
<br>
@indentBegin<br>
… swift code ...<br>
@indentEnd<br>
<br>
@commitCommentFragmentBegin<br>
… swift code ...<br>
@commitCommentFragmentEnd<br>
<br>
etc…<br>
<br>
Why encourage reinventing the wheel by pushing source to source transformations to tools of varying quality and completeness?<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div></div></div></div>