make klu backend work with new klujax#107
Merged
Merged
Conversation
Member
Author
|
We'll probably need to rerun the workflows after klujax 0.5.0 is released. |
cdaunt
approved these changes
Apr 15, 2026
cdaunt
left a comment
cdaunt
left a comment
There was a problem hiding this comment.
This is the simplest change. I had gdsfactory/klujax#29 in klujax placed in so you do not need to cast to jnp.int32 as maybe we want to enforce consistency there. I'm ok to merge. up to you if we want to change that small inconsistency
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only merge after klujax==0.5.0 has been released.