Update spec wrt. Polymorphism #790
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 15, 2024
* Move "Operation Extensionsibility" to after Type System (and up one level), rename to "Extension System" * Add Polymorphism section inside Type System: any `Function` type may be polymorphic * Clarify working of operations, including adding Appendix 3 with full details binary `compute_signature` * Add `OpaqueOp` as a dataflow node operation fixes #790
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At present the codebase allows FunctionType's to be polymorphic, so there is the possibility of polymorphic lambdas being around as first-class values, and FuncDefns (only) can declare TypeParams (perhaps a Const node containing a Hugr rooted at a FuncDefn could produce a value of such a polymorphic type?).
Although #285 argues for simplifying this (so Consts would only contain functions of monomorphic type, and only Static edges from FuncDefn nodes would be able to carry polymorphic types), we haven't done that yet, so that'll be another spec update if we do it...
The text was updated successfully, but these errors were encountered: