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.

Sign up for GitHub

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

Jump to bottom

Do we need backend.change_to() functionality? #114

Open

pnkraemer opened this issue Nov 16, 2022 · 0 comments

Labels

question

Owner

pnkraemer commented Nov 16, 2022

Are there use cases where we create a diffeqproblem with one backend, and (in the same application) change the backend and create more problems?

While doing this is currently possible, I am not able to come up with a scenario where one would need this.

If there are no use cases, I am tempted to simply remove the backend.change_to functionality.

pnkraemer added the question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment