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
For a 0.4.0 release #56
Conversation
remove unsafe use of dictionary in multithreading
Also trys avoids serializing by removing fetch
Avoids boxing of progressmeters and channels in learning curve generation
It appears from comments above that #57 (breaking) is required before this one. If so, can you please re-title this PR, reminding me what this PR does (remove dictionaries ?) |
Nevermind, I forgot this is already the dev branch. I'm going to merge this and #57 and just live with the extra breaking release. I have other updates I want to make here. |
Created a copy of range object for each thread since in general the user is allowed to define a more general range type(`<:MLJBase.Param`) which may behave much differently(e.g may be mutable) creating unwanted side effects.
@OkonSamuel Good catch, although I should not think a good idea (or good reason?) to have mutating range objects, and could add that to the docs. |
CPUProcesses
withinCPUThreads
(breaking)