aws-sdk-rust VS polars

The AWS SDK for Rust contains one crate for each AWS service - you can check them out here.

> What kind of plans for support of Rust's evolving async ecosystem?

We were hoping async-function-in-trait would land before GA, however, we have a plan to add support in a backwards compatible way when it's released.

> Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps?

Our roadmap has unfortunately been in a state of disrepair for some time. We're hoping to get it cleaned up and accurate post GA.

> Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically AWS SDKs have been inconsistent on. Just a request not really a question :-)

There are lots of examples here [1], some simple, some quite complex. If there's something you have in mind, please file an issue! Having great examples is one of our priorities.

[1]: https://github.com/awslabs/aws-sdk-rust/tree/main/examples

There’s a pretty nice example of this in the aws rust sdk here.

The official AWS Rust SDK still seems to be a work in progress(developer preview) with a warning to not use it in production.

i'm using https://github.com/awslabs/aws-sdk-rust heavily and was wondering if there was a more specific community (subreddit, Discord server, etc) of Rust x AWS developers?

Only relevant search result was this github issue, which didn't really solve the problem.

I went on rusoto just because aws-sdk-rust says at the beginning of the readme:

Official libraries for major cloud vendors will definitely boost Rust's adoption. aws-sdk-rust is still in 'developer preview', but it's getting there.

This is because 0.1 is in actuality the floating point value value 0.1000000000000000055511151231257827021181583404541015625, and thus 1 divided by it is ever so slightly smaller than 10. Nevertheless, fpround(1 / fpround(1 / 10)) = 10 exactly.

I found out about this recently because in Polars I defined a // b for floats to be (a / b).floor(), which does return 10 for this computation. Since Python's correctly-rounded division is rather expensive, I chose to stick to this (more context: https://github.com/pola-rs/polars/issues/14596#issuecomment-...).

https://github.com/pola-rs/polars/releases/tag/py-0.19.0

That turned out to be related to pola-rs/polars#11912, and this linked comment provided a deceptively simple solution - use PARSE_DECLTYPES when creating the connection: