[swift-corelibs-dev] incomplete implementation warning functions

Will Stanton willstanton1 at yahoo.com
Mon Jan 25 20:28:38 CST 2016

Hello Tony,

Thanks for your reply and sorry for my late one – I thought I could fix the whole file but then saw how long it was, and snow came. Oops!

I think the approach to future merges is very reasonable.
Still, I am skeptical log messages would be unbearable, especially once/run for debug.

Finally, some implementations seem hard to write without knowing how Apple Foundation does it, but I’ll save that for another day!

Will Stanton

> On Jan 21, 2016, at 6:38 PM, Tony Parker via swift-corelibs-dev <swift-corelibs-dev at swift.org> wrote:
> We’re in a somewhat tricky situation here where we want to enable incremental progress (and testability, so that prevents crashing), and yet I think it’s really important for users to understand when they’ve run across some code we haven’t implemented yet. I think in this case we should prioritize fixing the TODO and in future merges we should make sure it’s functional enough to work when merged, or crashes if you’re doing something that we haven’t yet implemented yet.

More information about the swift-corelibs-dev mailing list