-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use of internal package #5
Comments
The internal package is more for organization and cleanliness than functionality. It's all of the assembly code for vector operations specific to numgo. Since assembly isn't very user-friendly, I thought it best to keep it separate. I need to go through and put each asm function in its own file, as well. For development, it's much easier to add your fork's remote to the original clone than juggle different copies:
Then, the only change to your workflow is specifying the remote in push/pull commands.
|
Hi,
this is just for discussion, not a real bug or issue.
Is the use of a "internal" package needed/useful? I find it unnecessarily complicated to contribute, for every change I have to fork, pull fork, change package import path to my user, make changes, change package import back, push. Otherwise I get an error when trying to run the tests:
This might be a stupid mistake as I'm pretty new to go. Is there a common workaround for this rather than changing the import path in the code forth and back all the time? I must admit I don't really understand the code in that folder very well though.
The text was updated successfully, but these errors were encountered: