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
{{ message }}
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.
As we spoke last week, we have yet to come up with a resolution to the issue of the hdk proc macro package name. As we have it, the proc macro hdk is named hdk_proc_macro but since we are moving towards publishing it to crates.io we need o decide on the naming scheme. Should this be changed to hdk_v2 or should we keep it as hdk_proc_macro.
The benefits of hdk_proc_macro are that developers won't have to change the name in their toml however, the naming scheme is a bit weird as compared to hdk_v2
The text was updated successfully, but these errors were encountered:
I've just realized this isn't really possible in current Rust. Proc macro crates can only export proc macros so it is impossible to have a single HDK crate. This kinda sucks I think
For this reason though I argue strongly against hdk_v2 since consumers will always need both crates. Eventually we can just remove the old macros from the hdk crate
As we spoke last week, we have yet to come up with a resolution to the issue of the hdk proc macro package name. As we have it, the proc macro hdk is named hdk_proc_macro but since we are moving towards publishing it to crates.io we need o decide on the naming scheme. Should this be changed to hdk_v2 or should we keep it as hdk_proc_macro.
The benefits of hdk_proc_macro are that developers won't have to change the name in their toml however, the naming scheme is a bit weird as compared to hdk_v2
The text was updated successfully, but these errors were encountered: