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
Theoretically, we want two trait methods sets produce the same extension id, after the resolution of type aliases.
However, the type aliases can be defined out of the TokenStream that current proc-macro-attribute processed. So how we do with it?
And we also need a helper function/macro for "client" to easily specify the extension_id which matches the "server" side.
However, these types are concrete types.
Currently, the
extension_id
is simply calculated on AST level which is not stable. see:XCQ/xcq-extension/procedural/src/lib.rs
Line 171 in 3c0d9b4
Theoretically, we want two trait methods sets produce the same
extension id
, after the resolution of type aliases.However, the type aliases can be defined out of the
TokenStream
that current proc-macro-attribute processed. So how we do with it?XCQ/xcq-extension-fungibles/src/lib.rs
Lines 4 to 19 in 3c0d9b4
And we also need a helper function/macro for "client" to easily specify the
extension_id
which matches the "server" side.However, these types are concrete types.
XCQ/xcq-extension/tests/extension_executor_works.rs
Lines 113 to 117 in 3c0d9b4
The text was updated successfully, but these errors were encountered: