Rizumu Ayaka
Rizumu Ayaka
I have downloaded this repository and am having this problem as well. The system I am using is MacOS. 
I ran vitest bench, my modified apiWatch seems to be slower than the original apiWatch. However, I don't have experience in optimizing its performance. Are there any tips or documents...
Regarding the API design of `baseWatch`, I haven't made too many changes other than some new callbacks. It is basically the same as `doWatch`. If you have any better design...
I created another separate PR #10173 for `onEffectCleanup` in order to reduce the reviewing time cost and get merged faster.
`onEffectCleanup` has been implemented in 2cc5615, and the scheduler was recently refactored in #10407. I will update this PR to support these new changes, which may take some time.
Due to the obvious difference between `onEffectCleanup` in 2cc5615 and here, after communicating with Evan, I have renamed the API in this PR to `onWatcherCleanup`. It will not be deleted...
我支持大部分山前的观点。但是我希望补充我的感受。我感觉为坏死而丢失结构在愈合导致的外观问题不能算作外观的 feature，至少我无法接受目前得到的手术效果。
will fix at integrations v2.0
I am trying to implement this issue, I noticed that currently slot outlets need to be obtained through the instance, do we need to create a `createSlot` function to handle...
I think it is necessary, because for complex requirements such as dynamic slot outlets (``), encapsulating functions can reduce the complexity of generating code.