Gleb Kochergin

> @mweststrate @k-g-a any thoughts? Looks good to me. Do I get it right, that you just omitted beforeDetach/beforeDestroy from example above, but those are supposed to be present? )

> Before detach and before destroy would become optional disposers returned from the initiators as shown in the example actually, but that can be switched back easily if you think...

@mweststrate I'd like to draw your attention to this RFC as you've been showing decent activity in this repo lately :) We're heavily using MST for our new project. For...

Hi! For now, performance is not a big concern for our project as the current implementation works fast enough, but this eventually has to end. I still want to introduce...

Hi, @BrianHung! Unfortunatelly I don't have any artifacts left of those experiments. The code was too far away from being appropriate for pushing somewhere. The key idea was to define...

While impelmenting stuff described in #1355 I thought of adding special types `referenceArray`/`referenceMap`. Just a basic API overview: ```ts const myArrayType = types.array(SomeSubType); // it would be impossible to inline...

Even simpler API: ```types.arrayReference((self) => self.items, 'sync')``` - by having `self` we can always reference own tree's parts, but are free to get anything we want (as the last example...

I do incline to the latter [proposal](https://github.com/mobxjs/mobx-state-tree/issues/867#issuecomment-432372080) with API clearly mirroring mobx's one - it's dead simple and gives reasonable flexibility. Single setting (```runEffects```) looks acceptable and I can understand...

Can't think of any use cases for starting/stopping effects manually. It would be great to have an example.

```getTypeInfo``` approach seems more consistent with current reflection API (```getrPropertyMembers```, ```getMembers```). I'd modify returned value just a little bit to match the following interface: ```ts interface ITypeInfo { name: 'union'...