support nested memoize (2nd)

[dai-shi]

#4 was suboptimal and didn't work for the case I wanted to make work.

Instead of trackMemo, this propagates affected to parent memoize functions even if it's returning a cached value.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 046f24f:

Sandbox	Source
Vanilla	Configuration
Vanilla Typescript	Configuration
React	Configuration
React Typescript	Configuration

[dai-shi]

https://codesandbox.io/s/vanilla-typescript-forked-d83b8?file=/src/index.ts

@theKashey This is what I wanted and looks ok.

// will look again
console.log(
  getItemA({ state: prevState, id: 3 }) === getItemA({ state, id: 3 })
);

[theKashey]

👍 , this was a little issue for memoize-state, as nested memoization was doing parent one a little unstable - "affected" keys were changing every time.
I was considering something like touchAffected, but in my case, the underlying memoization was reselect based.

---

During memoize-state development I added a shallBePure helper, which just runs memoization twice to check that function is pure. Just to found that state access is a part of function pureness.

This touched moment is a missing piece. Thank's @dai-shi, I'll make my stuff a little bit touched as well.

[dai-shi]

I was just about to create a redux example, and found unexpected behavior. Maybe a bug... 🤔

[dai-shi]

https://codesandbox.io/s/proxy-memoize-demo-forked-fi5ni?file=/src/App.tsx
I finally made this work. I suppose this is the best we can do with proxy and weakmap combination.