<div dir="ltr">PS, for what it’s worth, i am the maintainer of the <a href="https://atom.io/packages/language-swift-89">language-swift-89</a> atom package.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 31, 2017 at 8:29 PM, Taylor Swift <span dir="ltr"><<a href="mailto:kelvin13ma@gmail.com" target="_blank">kelvin13ma@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Jul 31, 2017 at 7:20 PM, David Sweeris <span dir="ltr"><<a href="mailto:davesweeris@mac.com" target="_blank">davesweeris@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On Jul 31, 2017, at 3:59 PM, Taylor Swift via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> I’m gonna come out and say I’m not a fan of this at all. I’m already pretty suspicious of operator overloading, and I think supporting this would make Swift code much more difficult to read. Also, while for some reason everyone ignores this, this kind of syntax is almost impossible for text editors to highlight, which I think is an important consideration for any changes to language syntax.<br>
<br>
</span>As I said in some other thread, I'm not convinced we should be making design decisions based on potential aesthetic bugs in text editors. Not because syntax highlighting isn't important for non Xcode users, but because they're just that: bugs... Presumably they'll get fixed in the next release of whatever does your syntax highlighting.<br></blockquote><div><br></div></span><div>It’s not that I’m against new syntax, language packages can always be updated. But when it comes to introducing syntax that you cannot update a language package to support, I think that’s something to avoid. Most text editors parse source code using regular expressions. That’s not just a technical limitation, it’s also good sense. You don’t want to have to search for a keyword declaration that potentially lives in another file, or even another module, if it exists, just to know whether a word is an identifier or an operator.<br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Does anyone know if the new technologies that Xcode ties into are specific to swiftc/clang, or is LLVM in general now able to integrate with text editors for syntax highlighting, etc? This might be a hard sell if only works with Swift, but if it's a new service that LLVM provides for any language (or even just Swift & the Cs, given the laters' popularity), all your text editor's vendor has do is support that and it'll automatically get correct syntax highlighting info straight from the compiler itself.<br>
<br>
- Dave Sweeris</blockquote><div><br></div></span><div>This idea <a href="https://github.com/atom/atom/issues/8669" target="_blank">came up in the past</a> with Swift support in the Atom editor and it never went anywhere. Just because one single proprietary source editor supports the proposed syntax is not evidence that it would be widely supported. Considering Atom is one of the more progressive editors out there, if they weren’t going to support SourceKit integration I doubt the many other editors out there would. Mind you gedit literally <i>just</i> got basic regex Swift highlighting support about a month ago.<br></div></div><br></div></div>
</blockquote></div><br></div>