Skip to content

Conversation

@YingboMa
Copy link
Member

@YingboMa YingboMa commented Sep 2, 2020

Copy link
Member

@ChrisRackauckas ChrisRackauckas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will work to get it out the door. Let's make sure the same is done to StochasticDiffEq while it's on our minds.

@@ -1,4 +1,4 @@
mutable struct AutoSwitch{nAlg,sAlg,tolType,T}
mutable struct AutoSwitchCache{nAlg,sAlg,tolType,T}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in #325, it would make sense to make this immutable.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind. I see that this became the cache and that the struct below is immutable. I'll grab some coffee.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to bring it to full immutability to guarantee safety, but this is the quickest way to working so it's worth it for now. The plan is to probably have a GSoC to follow up and do more stiffness estimates, in which case we'll pick this back up and probably make it immutable, but at least if it's fully thread-safe already that can wait.

@ChrisRackauckas
Copy link
Member

It would be nice to have a test of thread-safety though... but that might be hard to cook up here.

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.

4 participants