-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Feature] Create a IRBuilder and ir_compiler_factory #4
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @kaosmicadei. Some (hopefully useful) comments from me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work @kaosmicadei, really nice. Minor cosmetic comments. I would pay attention to docstrings and layouts in general. Also, we can move to pytest if we want to run that on the CI 😬. Will approve in following but that should be relatively quick.
Co-authored-by: Roland-djee <[email protected]>
…ons (add, sub, mul, div, rem, pow)
…patible with "crossing-lattice" strategy and `PyQ` gridless model
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems good to me for now. We should move on with this to enable other libraries.
Currently, these helper functionalities aim to be used in the Qadence 1 syntax port. Later, they can be used to implement new input formats for Qadence 2 IR.
Closes #1