Ingvar Stepanyan
Ingvar Stepanyan
@dtolnay Well that should be solved when Rust implements constant-based generalization, although unsure how long it will take. Do you think users will be providing hardcoded JSON arrays that are...
Another issue I've currently run into is that it's needed to generate struct with type params for each given expression, and again, generating random names is hard and there is...
One more option would be, instead of elements, to put closure into the struct, and in that case `impl Serialize` would just call that internal closure, which in turn has...
@dtolnay Do you think we could limit keys to be just identifiers? That's what I did on our project and then things get much, much easier as you can just...
@dtolnay thought about tuples, but then we need to define serialization only for limited number of tuple sets, and specialized key-value records.
> Now I see that PR #14 exists... would it fix this issue? I don't know. As mentioned in comments, in its current state it breaks some other things and...
Or, you can try it out yourself and see if both `Option` and `serde(default)` still work.
cc @mfish33 This is an interesting one, and a bit unfortunate. I'm surprised those are referenced at top-level scope, I guess we need some way to retrieve them lazily instead.
> Further, it seems that this issue does not exactly have to do with Bigint types rather having rust bindings that receive u64/i64's as arguments or JS bindings that return...