Re: [swift-evolution] [Pitch] #error

> On Jun 12, 2017, at 3:57 PM, Daryle Walker via swift-evolution > wrote: > > >> On Jun 12, 2017, at 8:03 AM, Ben Rimmington > > wrote: >> >> >>> On 11 Jun 2017, at 19:15, Beta wrote: >>> >>> A proposal and implementation of #warning exist. It has been judged

Re: [swift-evolution] [Pitch] #error

> On Jun 12, 2017, at 8:03 AM, Ben Rimmington wrote: > > >> On 11 Jun 2017, at 19:15, Beta wrote: >> >> A proposal and implementation of #warning exist. It has been judged out of >> scope for Swift 3 and Swift 4 phase 2. >> >> https://github.com/apple/swift-evolution/pull/353 > > See also

Re: [swift-evolution] [Pitch] #error

> On 11 Jun 2017, at 19:15, Beta wrote: > > A proposal and implementation of #warning exist. It has been judged out of > scope for Swift 3 and Swift 4 phase 2. > > https://github.com/apple/swift-evolution/pull/353 See also "[Pitch] #warning" in the mailing lists:

Re: [swift-evolution] [Pitch] #error

A proposal and implementation of #warning exist. It has been judged out of scope for Swift 3 and Swift 4 phase 2. https://github.com/apple/swift-evolution/pull/353 > On Jun 10, 2017, at 10:15 AM, Daryle Walker via swift-evolution > wrote:

Re: [swift-evolution] [Pitch] #error

I was playing around with Swift's mysterious Builtin module, accessible via the `-parse-stdlib` compiler flag and I noticed a builtin primitive that causes a fatal error if the branch it's in is not optimized away. This seems like an opportunity for a much more powerful "this place is not implem

Re: [swift-evolution] [Pitch] #error

+1 on adding a compile-time error directive. #error seems like the right syntax as well. I had a maybe nit-picky comment about the proposal though. I think the example may not be ideal, since you could accomplish that compile-time error by annotating the method or class where that code lives with @

Re: [swift-evolution] [Pitch] #error

This is the best I've found for searching the archives: https://www.google.com/search?q=site%3Ahttps%3A%2F%2Flists.swift.org%2Fpipermail%2Fswift-evolution%2F+%22%23error%22 On Sun, Jun 11, 2017 at 11:30 AM Daryle Walker via swift-evolution < swift-evolution@swift.org> wrote: > > > On Jun 10, 20

Re: [swift-evolution] [Pitch] #error

Nate Cook staged a Discourse server that is searchable for a portion of the archives. A quick Google search will get you there, although at the moment lists.swift.org doesn’t seem to be responding, so I can’t send you the link off-hand. For threads outside the range of that resource, I‘d recommend

Re: [swift-evolution] [Pitch] #error

> On Jun 10, 2017, at 2:00 PM, Xiaodi Wu wrote: > > Daryle, there have been several pitches in the past with respect to #error, > and very enlightening arguments both for and against the idea have been > eloquently written. > > Since you’re resurrecting this idea, could I suggest going back t

Re: [swift-evolution] [Pitch] #error

Daryle, there have been several pitches in the past with respect to #error, and very enlightening arguments both for and against the idea have been eloquently written. Since you’re resurrecting this idea, could I suggest going back through the archives and linking to and summarizing these argument

Re: [swift-evolution] [Pitch] #error

Love it! Except I'd add `warning` as well. > On Jun 10, 2017, at 8:15 PM, Daryle Walker via swift-evolution > wrote: > > Unconditional Error Messages > Proposal: SE- > Authors: Daryle Walker , Author 2 > > Review Manager: TBD > S

[swift-evolution] [Pitch] #error

Unconditional Error Messages Proposal: SE- Authors: Daryle Walker , Author 2 Review Manager: TBD Status: Awaiting review During the review process, add the following fields as needed: Decision Notes: Rationale