Memory leak when definition unshared true about di HOT 7 CLOSED

Hello,
unshared objects are still stored in the container. This was done because they may need to be closed when the container is deleted.
You can try the branch https://github.com/sarulabs/di/tree/speed_improvements
This is a complete rewrite of the project to improve performance.
On this branch only unshared objects with a close function are stored in the container.
This should resolve your issue.
If this work I will considerer merging this branch on master. I wanted to document the new features before doing so. But it has been more than a year now and I could not find the motivation.

from di.

Thank you, I think this can resolve my issue.

I think this is very great library, if this compare with another DI library in Go because is very easy to use and very simple.
Maybe this can give you motivation wkwk

from di.