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

Is this tool abandonware? #17

Closed
sleaze opened this issue May 18, 2017 · 10 comments
Closed

Is this tool abandonware? #17

sleaze opened this issue May 18, 2017 · 10 comments

Comments

@sleaze
Copy link

sleaze commented May 18, 2017

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?

@gm42
Copy link

gm42 commented Aug 10, 2017

I found the same issue and decided to start maintaining a fork here:

@ryan0x44
Copy link

gometalinter is using https://github.com/alecthomas/gocyclo by @alecthomas because PR #1 hasn't been merged

@gm42
Copy link

gm42 commented Sep 22, 2017

@ryan0x44 what do you estimate is the impact of (the lack of) #12? I am not academically versed on the topic but I thought it's quite big, thus decided to make that fork.

@ryan0x44
Copy link

ryan0x44 commented Sep 26, 2017

@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?

@gm42
Copy link

gm42 commented Sep 26, 2017

@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?

@nodirt
Copy link

nodirt commented Sep 27, 2017

I think we should be discussing the problems with #12 in #12. I've addressed the concerns in the PR and explained why I believe that the current implementation is incorrect.

@gm42
Copy link

gm42 commented Nov 7, 2017

After the discussion in #12 I have retracted it from my fork; it still would be nice for the tool to be actively maintained.

@ghostsquad
Copy link

any word on whether or not this tool or the fork are abandoned?

@opencloudengineer
Copy link

I see some activity on the repo recently.

Even though there has been a lot of activity (code push) on this repo since this issue was created, and that's why @fzipp can you please once, confirm here on this issue if this project has been abandoned, and if not then please close this issue.

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. 🙏

@fzipp
Copy link
Owner

fzipp commented Nov 7, 2021

Hi @opencloudengineer,

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.

I'd love to raise an issue and create PR for it.

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).

@fzipp fzipp closed this as completed Nov 7, 2021
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

7 participants