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

For a 0.4.0 release #56

Merged
merged 95 commits into from Jun 26, 2020
Merged

For a 0.4.0 release #56

merged 95 commits into from Jun 26, 2020

Conversation

ablaom
Copy link
Member

@ablaom ablaom commented Jun 11, 2020

  • Updates for MJLBase 0.4
  • Add restrictions on nesting CPUProcesses within CPUThreads (breaking)
  • Remove unsafe use of dictionaries in multithreading

@ablaom ablaom closed this Jun 25, 2020
@ablaom ablaom reopened this Jun 25, 2020
@ablaom
Copy link
Member Author

ablaom commented Jun 25, 2020

@OkonSamuel

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

@ablaom
Copy link
Member Author

ablaom commented Jun 25, 2020

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.

@ablaom ablaom changed the title For a 0.3.7 release For a 0.4.0 release Jun 25, 2020
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.
@ablaom
Copy link
Member Author

ablaom commented Jun 25, 2020

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

@ablaom ablaom merged commit fcc05fa into master Jun 26, 2020
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

Successfully merging this pull request may close these issues.

None yet

2 participants