Ingvar Stepanyan
Ingvar Stepanyan
> I don't think either is more simple, just different presentation. Right, it's just about moving checks earlier so that such mismatch could be reported by parsers rather than validators.
Is this more or less continuation of #106? If so, might be better to reopen that one since it already had lots of interesting discussion around lifting this restriction. Anyway,...
> The wording "potential for abuse" reads like a concern of "people will get lazy and write 'bad practices' synchronous code" It's not - my concern is "people will unknowingly...
I'm on my phone on a weekend, so I won't be responding to individual questions right now, but the beginning seems suspicious as if we're still talking about the same...
FWIW I'm currently doing this with newtype, which generally works pretty well: ```rust pub struct ProductionSetItem(Production); impl Deref for ProductionSetItem { type Target = Production; fn deref(&self) -> &Production {...
> When you want to avoid the hop of encoding a Rust type to JSON and then deserializing it again. That said, this might actually be faster for complex object...
> When you're dealing with ArrayBuffers This is also covered by proper serde integration - it has dedicated methods for serializing / deserializing bytes (usually via https://github.com/serde-rs/bytes) and I'm already...
I see. It sounds like your main concern is the boilerplate associated with defining custom types for one-off objects, even if objects themselves are still static. If so, you should...
> I thought that objects such as ArrayBuffers can be passed between JS and Rust, without (de)serializing at all? Unfortunately not, you still need to copy the memory from JS...