Yuriy Pitomets

I can't migrate to _Swift_ until it have backward binary compatibility. Anyway, _ObjC_ still here, and would be nice to have type safe `map:` for it too.

ok, thank you for answer; propose leave the issue open for now then.

FYI /me still use ObjC RAC because of stability (for framework), as I know, there's some issues with Swift compiled libraries with linking and backward compatibility. So it would be...

But currently it installed with `Overcoat+ReactiveCocoa` with no problems, so closing this issue for now. Thanks.

Would you switch this library to modern `ReactiveObjc`?

Is it possible to implement such behaviour with current codebase to avoid a lot of code duplication on each validated property? Can't figure out it by myself because of heavy...

Backtrace: ``` frame #1: 0x0000000100ffb614 ReactiveObjC`-[RACDisposable dispose](self=0x000060800021bc80, _cmd="dispose") + 180 at RACDisposable.m:81 frame #2: 0x0000000100ffa948 ReactiveObjC`-[RACCompoundDisposable dispose](self=0x00006080004c26f0, _cmd="dispose") + 328 at RACCompoundDisposable.m:239 frame #3: 0x0000000100ffa948 ReactiveObjC`-[RACCompoundDisposable dispose](self=0x00006080016d24b0, _cmd="dispose") + 328...

Why when I do ```objc [subject sendNext:@2]; ``` `RACSubscriber` do ```objc - (void)dealloc { [self.disposable dispose]; } ``` so my task being cancelled.

Problem flow: `subject next` => `disposable dispose` => `task cancel` => `task error` => `subscriber error` => `break subscription`.

Ok, _fixed_ by replacing `flattenMap:` by `map:` plus `switchToLatest`. Leave issue here because not sure is it right behaviour or bug. Please, check.