We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
golang/go#33848 will be released in 1.14 (tentative deadline February 1), let's switch to modules!
No need to block the Oragono 1.3 release on this, but we'll see how it goes.
The text was updated successfully, but these errors were encountered:
Switching to modules, means that each modulce can be loaded/unloaded? via conf file? while running ( and rehash )? If so, this is great!
Sorry, something went wrong.
Sorry, totally unrelated to that, it's just a new dependency management / build system :-)
https://blog.golang.org/using-go-modules
The goal is that all functionality should be controllable via conf and rehash. It shouldn't be necessary or desirable to unload the code.
Our 1.3 slipped far enough that we might as well do this now, before #779 and #348 :-)
634470b
slingamn
No branches or pull requests
golang/go#33848 will be released in 1.14 (tentative deadline February 1), let's switch to modules!
No need to block the Oragono 1.3 release on this, but we'll see how it goes.
The text was updated successfully, but these errors were encountered: