On Jul 6, 2015, at 13:10 , Rick Aurbach <r...@aurbach.com> wrote: > > So my question: does this make any sense?
If I was going to Swift-ify the Event concept, I wouldn’t use an enum *inside* an Event object, I’d use an enum (with associated values) *instead of* an Event object. In the context of Core Data, this would similar to creating a custom scalar property that’s backed by a Core Data property, which is not hard but incredibly badly documented in the Core Data reference guide. But since this is Core Data, I’m not sure it’s a good idea to add an eighth hell to the seven you’re in already. It may be better to stick to whatever is most natural for Core Data, which is whatever you’d do in Obj-C. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
