> On Jun 27, 2016, at 1:58 PM, Charles Srstka via swift-evolution
> <[email protected]> wrote:
>
> Obviously, I’m in favor of this one. +1!
>
> I think I did prefer the older name of CustomUserInfoError for the
> domain/code/userInfo protocol, rather than CustomNSError. This is just
> because I’d like to be able to do a global search through my project for
> “NSError” and have it turn up empty. Maybe a silly reason, I know. ;-)
I’m floating CustomNSError as the protocol name because I don’t feel that
domain, core, or userInfo are fundamental to the Swift error model—they’re
about exposing things specifically to NSError.
- Doug
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
