Ah :-) Yes that could lead to unexpected behaviour of the IDE. However I would not qualify that as dangerous. The code is indeed excluded as was the intention. Re-introducing the #pragma for that purpose seems a bit OTT to me.
Rien. > On 05 Sep 2016, at 10:37, isidoro carlo ghezzi <[email protected]> > wrote: > > I have this code: > ``` > let tuple = ( > MARK: 1, > EXPLODE: true, > DO_SOMETHINGS_UNDEFINED: true > ) > ``` > > If I comment it, because I want to exclude that code to be compiled: > > ``` > // let tuple = ( > // MARK: 1, > // EXPLODE: true, > // DO_SOMETHINGS_UNDEFINED: true > // ) > ``` > > what will happen to the IDE? > Commenting that code, I didn't mean to give strange instructions to the IDE. > > Isidoro. > > On Sep 05, 2016, at 07:16 AM, Marinus van der Lugt <[email protected]> > wrote: > >>> >>> I understand that maybe a compiler shouldn't lose time handling `#pragma >>> options`, but giving semantics to source comment, I think it can be >>> dangerous and misunderstood. >> >> Could you elaborate what could be dangerous or misunderstood? >> >> Rien. >> _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
