Jake Goulding

> More generally, `-> impl Trait` is impossible to use for a static. I don't follow why [my comment almost immediately above yours](https://github.com/rust-lang/rfcs/issues/1349#issuecomment-558326250) does not apply: ```rust #![feature(impl_trait_in_bindings)] use once_cell::sync::Lazy;...

Same problem and resolution here: - ✅ dev build works fine - ❌ production build with `@parcel/optimizer-swc` has missing symbols - ✅ production build with `@parcel/optimizer-terser` works fine

Likewise, I'm using `type="module"`: ```html ``` That being said, I have noticed that I get two output JS files: ``` ui/dist/ui.0a6c46e3.js 415 KB 1.63s ui/dist/ui.6eb97b68.js 415.06 KB 1.65s ``` Which...

You can use [`AsyncBencher::method.iter_custom`](https://docs.rs/criterion/latest/criterion/struct.AsyncBencher.html#method.iter_custom). Something like: ```rust .iter_custom(|| async { s3_put().await; let start = Instant::now(); s3_get_single(file).await; start.elapsed() }); ```

This isn't an enhancement, but a bug report: > I also found some inconsistencies with respect to popcnt / lzcnt / abm that AFAICT none of the libraries handle properly.

There’s nothing special about an inspect that has the whole value that should be limited to `Result` — any type whatsoever could apply. That’s the tap crate https://docs.rs/tap/latest/tap/

I tracked this down for a [StackOverflow question](http://stackoverflow.com/questions/20843691/openssl-problems-in-jruby/20861277#20861277). I believe the root problem is that this gem packages the `bcprov` JAR with a version of Bouncy Castle that is incompatible...

I think it's likely to be related to [`OverwriteOnNil`](https://github.com/apotonick/representable/blob/v3.0.0/lib/representable/deserializer.rb#L22-L24). This returns `Representable::Pipeline::Stop`, which is then [returned from the pipeline iterator](https://github.com/apotonick/representable/blob/v3.0.0/lib/representable/pipeline.rb#L11).

Any suggested areas of Reform or it's dependencies you suggest I poke around in? Any kinds of test cases that would be useful to provide?

> like features = ["automotive"] to enable them. Is there a reason to ever compile anything but the current one? It kind of seems like *every* mcu should be a...