Add support for keepAlive

[weiwei-lin]

Feature request Support equivalent of @computed({keepAlive: true}). Note that keepAlive from mobx-utils isn't the same. Since it causes the computed value to always be re-evaluated even there's no other observers.

Is your feature request related to a problem? Please describe.

The lack of computed support make the friction of migrating from MobX to MST a lot higher. And given that MST use a tree-like structure for managing states, arguably the chance of memory leak is even lower.

Are you willing to (attempt) a PR?

• [x] Yes
• [ ] No

[coolsoftwaretyler]

@weiwei-lin - kind of like I mentioned in #1950 - are you still having trouble with this/interested in opening a PR? I don't know if I understand all the implications of this feature request, but I'd be happy to talk with you about it if it's still on your mind all this time later.

[cmdcolin]

i ran into a similar issue that i saw in a data intensive app that uses mobx-state-tree that i found. the full "scenario" that i was seeing was:

1) while scrolling the app, it was unexpectedly slow (there were very noticeably scroll jankyness) 2) when i did performance tracing, i saw it was calling a MST getter (e.g. "get mySlowMethod() {...}") repeatedly during the scrolling stuttering 3) i thought, odd....why is that 4) i added a trace() statement in the getter (via import {trace} from 'mobx') 5) the trace() statement repeatedly was printing a statement like "'mySlowMethod' was suspended and it will recompute on the next access." during the scrolling stuttering 6) i fixed it by adding a blank autorun that is a blank "usage" of the observer

  .views((self) => ({
    get mySlowMethod() {
      /* this is a heavy computation or is slow */
    },
  }))
  .actions((self) => ({
    afterAttach() {
      addDisposer(
        self,
        autorun(() => {
          console.log(self.mySlowMethod); // this simple method of making sure to access self.mySlowMethod keeps the slow getter alive. you can alternatively not console.log it and do something else with it if needed, just make sure to access it in an autorun
        }),
      );
    },
  }));

i posted about it here also https://github.com/mobxjs/mobx/discussions/3911

[coolsoftwaretyler]

@cmdcolin - thank you so much! That's very useful insights. Also somewhat related to https://github.com/mobxjs/mobx-state-tree/discussions/2161, where the whole "observe it even if you don't do something with it" workaround keeps a computed value around.

I like this idea a lot. I will keep it labeled as help/PR welcome, because I'd welcome a PR implementing something like this. Although I do wonder if that's something more appropriate in the MobX side of things. Maybe both projects trying an implementation will lead to a best case scenario.

Really appreciate your time, and I'd welcome anyone reading this to reach out if they want to try implementing it. I am always happy to get people started contributing.