Skip to content
New issue

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

Allow adding custom ToKey implementation #1291

Closed
vasyafromrussia opened this issue Jan 16, 2025 · 0 comments · May be fixed by vasyafromrussia/near-sdk-rs#1
Closed

Allow adding custom ToKey implementation #1291

vasyafromrussia opened this issue Jan 16, 2025 · 0 comments · May be fixed by vasyafromrussia/near-sdk-rs#1

Comments

@vasyafromrussia
Copy link

In our Fungible Token smart contract we need to resolve LookupMap keys in a special way. It made us fork near-sdk-rs to add the LookupMapAdapter. The necessity of this decision is due to the fact that ToKey implementations are sealed here, and we cannot instantiate LookupMap using with_hasher.

So I wonder what's a reason behind sealing these implementations, and probably it's worth to get rid of this sealing and allow custom implementations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Shipped 🚀
Development

Successfully merging a pull request may close this issue.

1 participant