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

findpkg: if we drop support for Go 1.13, can this code be removed? #61

Closed
hugelgupf opened this issue Jan 5, 2022 · 4 comments
Closed

Comments

@hugelgupf
Copy link
Member

If we drop support for Go 1.13, can this code be removed?

There's a comment here I wrote a long time ago which refers to a section of code that only exists because of Go 1.13: Lines 172-205

However, this could still be useful because we emit these skip notes as part of the build.

If I remember correctly, when you look up a package that doesn't fit any build criteria through packages.Load on Go >=1.14, you'll get a similar error message. Maybe we can delete the code and emit a similar error message in those cases? I think this needs some experimentation.

(E.g. I don't think we want to turn those warnings into errors, which would happen if we just delete the code.)

@MDr164
Copy link

MDr164 commented Feb 14, 2022

To add to that, should we maybe bump the minimum Go version to something more recent like 1.16 instead of keeping 1.13 around or are there other reasons to still keep 1.13 as the minimum version?

@hugelgupf
Copy link
Member Author

I typically don't bump the minimum version until I find something that makes the tests fail before version 1.x or whatever.

I see a tangible reason here: 1.13 is old and we could gain some simplification (maybe). I'd bump to 1.14. But I don't see a reason to exclude 1.14 yet other than "it's older than 1.15".

@MDr164
Copy link

MDr164 commented Feb 15, 2022

Got it. Thanks for clarifying!

@hugelgupf
Copy link
Member Author

Solved by #79.

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

2 participants