-
Notifications
You must be signed in to change notification settings - Fork 81
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
Is this tool abandonware? #17
Comments
I found the same issue and decided to start maintaining a fork here: |
gometalinter is using https://github.com/alecthomas/gocyclo by @alecthomas because PR #1 hasn't been merged |
@gm42 that PR seems pretty dense (lots of "cosmetic" changes in addition to logic changes) and the description doesn't actually describe the change, so I find it hard to estimate. Did you perform and comparisons of output with and without the changes? |
@ryan0x44 I do not see the bulk of cosmetic changes (maybe we just have a different threshold to judge), but what I noticed is the replacement of the AST/parser with SSA, and the new formula of course (both big changes). I did a comparison, and the calculated complexity was smaller on average for the code I checked it on; I picked it because I understood that current gocyclo uses an arbitrary formula rather than the correct one. @nodirt care to comment? |
After the discussion in #12 I have retracted it from my fork; it still would be nice for the tool to be actively maintained. |
any word on whether or not this tool or the fork are abandoned? |
I see some activity on the repo recently. Even though there has been a lot of activity I'd love to raise an issue and create PR for it. PS: Thank You @fzipp for the tool, this has been and still is really helpful for me in my Golang learning and development process. 🙏 |
thank you for your interest. The project was dormant for a while, but it's not dead. I keep the status quo up-to-date with developments in the Go ecosystem like modules and the upcoming type parameters, and I have reviewed and accepted some improvements since this issue was created, although one PR is still open. So I will close this issue.
If it's a feature request and not just a bug fix, please create an issue before implementing and submitting a PR, so that I and potentially others can weigh in on wether it's in the scope of the project before you do the work, so that your effort is not wasted (unless you need it anyway in a personal fork). |
There are unmerged PR's open for nearly half a year. Is this still being supported or should it be forked to someone who is able to maintain it?
The text was updated successfully, but these errors were encountered: