daxpedda

> > > No. In JS, the best we have are [common](https://www.robinwieruch.de/javascript-naming-conventions/) [naming](https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Writing_style_guide/Code_style_guide/JavaScript#function_names) [conventions](https://google.github.io/styleguide/jsguide.html#naming). > > > > > > Hm, that's bad. > > Yep. But if we take...

> > we might want to consider not converting anything that matches naming conventions. E.g. Struct and enum types should be pascal case in both languages, so if the user...

@tarcieri, follow-up from https://github.com/RustCrypto/traits/issues/2011. Would the same issue apply here with different messages being produced by the closure?

> X11 sits on top of the I/O stack and every I/O function is fallible. So every winit function would also need to return a Result. Not that I oppose...

When I start cleaning up Fabruic I will move all `TODO`s from the code into issues, this is one of them.

~~I marked Web as fixed, which was done in #2817.~~ ~~As far as I know all the other backends were addressed as well in #2817.~~ ~~I think this can be...

Nice catch! I think we should keep `publish.rs` only for bumping the version. With workspace publishing we can just slap `publish = false` on everything we don't want to publish...

That would be great as well!

> Has there been any previous discussion around exposing these? See https://github.com/WebAudio/web-audio-api/issues/2499. > Technically as of [f09648a](https://github.com/whatwg/encoding/commit/f09648a96ef4cffbf68734a5f81b7ececf2e311e) they are exposed there. I can see in that surrounding discussions there seems...

We can't stabilize the `convert` or `describe` module because we would then be unable to break the encoding format, which is exposed there. I think there are some traits in...