You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ss2165 May 19, 2023 @ss2165
16 May 2023
Linking happens by looking up functions by name - therefore it seems the name should not just be metadata (I don’t think linking should rely on metadata)
I’d be happy with that. The alternative would be - the metadata may contain data that affects other tools (that operate on the Hugr), right? So we just have to say that the linker is an”other tool”….
Closes#136
drive-by: cargo update (hugr 0.13.2)
I have tested the test in
quantinuum-dev/guppy-integration#19 now passes and the
example has expected behaviour with crz oracle.
Closes#136
drive-by: cargo update (hugr 0.13.2)
I have tested the test in
quantinuum-dev/guppy-integration#19 now passes and the
example has expected behaviour with crz oracle.
Discussed in #72
Originally posted by ss2165 May 19, 2023
@ss2165
16 May 2023
Linking happens by looking up functions by name - therefore it seems the name should not just be metadata (I don’t think linking should rely on metadata)
@ss2165
16 May 2023
I think this means that declare/alias_declare should hold names, and that these operations are only valid at module level.
@acl-cqc
16 May 2023
I’d be happy with that. The alternative would be - the metadata may contain data that affects other tools (that operate on the Hugr), right? So we just have to say that the linker is an”other tool”….
@acl-cqc
16 May 2023
Also, we will need some kind of namespacing on these names, right?
The text was updated successfully, but these errors were encountered: