Ingvar Stepanyan
Ingvar Stepanyan
> and others are just kept unsupported Yes, but currently encoder lazifies all of them, which, like with other mentioned cases, can lead to producing BinaryAST that won't be actually...
This issue is just particularly high-priority for CDN-wide testing, because, if we enable encoder by default on CDNjs or unpkg.com, then it can currently break lots of assets with no...
> so, if treating lazy getter as eager getter in multiplart format is high-priority No, it's not particularly that part that is high-priority but the general "we have things produced...
FWIW this is a standard representation of negative numbers in JS parsers, as syntax spec technically doesn't define negative numbers. I agree it can be more efficient in custom formats...
Actually disregard the deleted comment, I didn't see that Shift already converts any keys to strings.
Indeed. If there is enough interest, I suppose we could expose it under a feature flag, but I'm hesitant of making the base crate larger (due to async machinery) for...
Is this related to #31? If you're running tests on the main thread, it probably won't work.
Also - just to check - are you building with all the necessary flags as described in the docs?
> And I've all the necessary build flags (or I would have compile errors). Not really, I think without some of the flags you'd simply get runtime errors as that's...
> The problem with this is that it makes thinks like `clippy check --all-features --all-targets` not usable (without some hacks), > and in turn complicates dev and CI workflows of...