<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Just to play devil’s advocate (since I am honestly ok with the less draconian form of the proposal now), wouldn’t it be possible to declare the relevant unicode characters in the module’s plist (or similar file)? I know it isn’t the most elegant solution, but it does move the bar on using those characters from impossible to possible, and it would no longer mix up the compilation layers.<div class=""><br class=""></div><div class="">Thanks,</div><div class="">Jon</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 24, 2016, at 10:10 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 20, 2016, at 5:03 PM, Jonathan S. Shapiro via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 20, 2016 at 12:25 PM, Jonathan Hull via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Would it be possible to do the following:<br class="">
<br class="">
• Have 1 group which are always used as identifiers. This would probably be the identifiers from this proposal.<br class="">
<br class="">
• Have a 2nd group which are always used as operators (quite a bit larger than the group proposed by this proposal). At a minimum, the following ascii + set operators + math operators:<br class="">
(± ≠ ≤ ≥ ¿ ¡ ™ ¢ ¶ • ° ƒ © √ ∆ ◊ § ≈ ∫ ÷ ¬ ).<br class="">
<br class="">
• Everything else is in a 3rd group. </blockquote><div class=""><br class=""></div><div class="">No. This is far, far too complicated, and it mixes up the layers of the compilation process.</div></div></div></div></div></blockquote><br class=""></div><div class="">Right. Any proposal that changes parser behavior based on a visible operator declaration will break the ability for Swift to separately compile files. This will have massive tooling ramifications that are almost certainly a non-starter.</div><div class=""><br class=""></div><div class="">-Chris</div><br class=""></div></div></blockquote></div><br class=""></div></body></html>