We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now there are 3 places where entry points (i.e. Wasm exported functions) are created:
use cosmwasm_std
cosmwasm_vm_version_4
allocate
deallocate
create_entry_points!
init
handle
query
create_entry_points_with_migration!
migrate
This model does not scale. But it is probably not great anyways to require this central place where all entry points are collected.
Instead we can decorate the entrypoints directly with something like this:
#[entry_point_init] pub fn init( deps: DepsMut, _env: Env, info: MessageInfo, msg: InitMsg, ) -> Result<InitResponse, HackError> {
This becomes very useful with #692 and #693.
The text was updated successfully, but these errors were encountered:
webmaster128
Successfully merging a pull request may close this issue.
Right now there are 3 places where entry points (i.e. Wasm exported functions) are created:
use cosmwasm_std
createscosmwasm_vm_version_4
,allocate
,deallocate
create_entry_points!
macro createsinit
,handle
,query
create_entry_points_with_migration!
macro createsinit
,handle
,query
,migrate
This model does not scale. But it is probably not great anyways to require this central place where all entry points are collected.
Instead we can decorate the entrypoints directly with something like this:
This becomes very useful with #692 and #693.
The text was updated successfully, but these errors were encountered: