Nick Tymchenko

@apparentsoft Thanks a lot for the detailed replies! Regarding parent-child contexts... Well, yeah, I was thinking about it a bit more and became pretty unsure about it myself. I'm using...

I just took an example for `findAll:` from the spec and modified it a bit like this: ``` [[[[RACSignal return:@1] doNext:^(id x) { NSLog(@"hi!"); }] findAll:Parent.entityName] subscribeNext:^(id x){ completed =...

Yeah, this one should work. I'm not sure if it's worth its money, though. As you pointed out, `-fetchWithTrigger:` seems like a better and more obvious way of achieving this...

Let's do it! And also the context method renaming part. Actually, I feel like I want to rename `- (NSManagedObjectContext *)mainContext;` and `+ (NSManagedObjectContext *)contextWithMainContext:(NSManagedObjectContext *)mainContext;` too because the term...

This method is supposed to work the other way around - it may be used to update your model with the values from the existing managed object. Frankly, I don't...

This is true, but for that I need at least one named argument. Which I cannot afford given the way things are now :)

From what I read about the blocks implementation, I understood that behind the scenes, the block descriptor itself is the named argument passed to the invocation function. Perhaps this could...

It looks like I got something working :) ``` @interface Foo : NSObject @property (nonatomic, assign) char *type; @property (nonatomic, readonly) void (^bar)(); @end @implementation Foo - (void (^)())bar {...

@liuyaouestc That's true. The above approach assumes you know the correct argument type before the call.

+1 would be much appreciated :+1: