rust-foundation-community-grant VS uom

That's a topic where already some work exists. You might want to checkout my collection of bad error messages from such trait heavy crates for example. It's important to notice that most of these errors look complicated, but mostly have a quite simple cause. In some of these cases it's even possible to reword these error messages by removing most of the complicated looking type stuff to something much simpler which then is easier to understand.

As with everything in static type checking, the upfront costs seem high (deciphering type errors can be a bit daunting for both diesel, and to a certain extent dfdx), but I feel like (1) this will get better (especially with the work /u/weiznich is doing), and (2) history has shown the upfront costs are worth it (as evidenced by the takeover of typescript and typed Python).

This change is hopefully only the starting point to a number of future improvements. I've got a project grant as part of the rust foundation community grant program to work on improving the error messages for trait heavy crates like diesel. Hopefully this will result in other improvements as well. I track this work here. If you hit bad error messages with diesel or any other trait heavy crate, please fill an issue there.

axum does basically ]the trick as bevy](https://docs.rs/axum/latest/axum/handler/trait.Handler.html#impl-Handler%3C(T1%2C)%2C%20B%3E) to emulate variadics and someone already filed this https://github.com/weiznich/rust-foundation-community-grant/issues/2

uom (type-safe zero-cost dimensional analysis) v0.35.0 got released today!

It happened! v0.34.0 (crates.io) has been released.

My hope is to release uom (type-safe zero-cost dimensional analysis) v0.34.0 this week. There have been a huge number of new quantities and units added since v0.33.0.

I have been reviewing lots of PRs recently submitted to add many new units and quantities to uom (type-safe zero-cost dimensional analysis).

I reviewed some PRs to add new units to uom (type-safe zero-cost dimensional analysis) yesterday and am really hoping to make progress on logarithmic units this week. no_std support is slowing down the later.

Working on a PR to uom (type-safe zero-cost dimensional analysis) to support logarithmic units.

A great type system enables things like unit preserving calculations and Formal Methods.

Is it the error messages, or other parts of uom that make it unwieldy to use? Feedback welcome here or as a new issue.

I'm working through reviewing the open PRs for uom (type-safe zero-cost dimensional analysis).