Closed Fraser999 closed 1 year ago
Do you have an idea what constrains no_std
code has in this context? Do I understand correctly it will prevent us from using String and Vec?
One of the things that was added after the fork was correct escaping of strings, wight requires us to use String
I guess.
Why do you need no_std support for this library? Can you give a use case?
I would recommending just using serde-json-core in that case unless there is a strong reason why you cannot
Actually, there's no longer a need for this. The use case was originally a no-std Wasm smart contract, but an alternative approach was taken.
Thanks for responding anyway, but I'll close this issue now.
See also #58
I have a use case for this crate, but I need to support
no_std
environments.I see this project is forked from serde-json-core and the first PR was to remove support for
no_std
. I'm wondering if there's any interest in moving back to supportingno_std
(behind a feature gate I expect). If so, I'd be happy to submit a PR here.