> On 6 Jan 2017, at 23:15, David Sweeris via swift-evolution > <swift-evolution@swift.org> wrote: > > >> On Jan 6, 2017, at 2:58 PM, D. Felipe Torres via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> Yeah, it was meant as a joke. >> I'm well aware of the uses you write about, I do that myself but felt like >> doing this piece based on the particular use case described in the "proposal" > > > I wouldn’t be horribly opposed to adding a function called “willItToCompile”, > “compileAnyway”, “noSrslyIDontCare”, or some other equally explicit name, > simply because that way it’d be easy to ensure that all such code was > revisited before shipping the product. > > I wouldn’t be horribly in favor, either, because putting a special phrase in > the string that you pass to fatalError() does the same thing, and doesn’t > complicate the language.
There's already NSUnimplemented for this kind of use case, and NSRequiresConcreteImplementation for catching subclasses that fail to implement a required (but perhaps optional) method, although these are statement based rather than expression based. Alex
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
