Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance Status and Ownership #38

Open
macisamuele opened this issue Mar 16, 2024 · 0 comments
Open

Maintenance Status and Ownership #38

macisamuele opened this issue Mar 16, 2024 · 0 comments

Comments

@macisamuele
Copy link

Hello @Aeledfyr,
I'm currently starting using this project and I find it very interesting and powerful, but sadly apparently unmaintained.

In the rust ecosystem it seems that we have a few similar libraries namely:

  • get-size: which has the drawback of not properly accounting for reference-counted instances
  • heapsize: which is no longer maintained and replaced by malloc_size_of which is not public and even attempting to clone the repo locally the usage experience is not very simple
  • memuse: which requires manual code writing to determine heap size of objects, provides boundaries and seems to be not maintained as well
  • ...

Given that in terms of easy to use this library is by far better than others (personal opinion) and that it seems to not be actively maintained I was wondering if I could do anything to support you with that.
Maybe I could help address the open PRs, support to create CI integration to have continuous testing and automated release (after tagging) such that we could maintain the library again.

Let me know what you think before investing significant time on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant