Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
-
sqlx
🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite. (by launchbadge)
Basically the TLDR is with these two properties I can guarantee that indices will always be valid, so I would like to skip bounds checking. Before creating such a thing myself, (which admittedly is not that complex), I was wondering if anyone knew of something like that which already existed. I checked crates.io but couldn't really find anything.
I've tried translating the example you posted to Rust, here is the code. It's lacking the DLL loading code, so it doesn't actually work (it compiles, but won't give you any results), but maybe with this you can kinda see the pattern for how to work with Rust + Windows API.
The windows-rs crate shows you some of the basics, and you can look at the windows-samples-rs repo for more info.
The windows-rs crate shows you some of the basics, and you can look at the windows-samples-rs repo for more info.
Another thing is, miri warns about undefined behavior on this code *(version_file.as_mut_ptr() as *mut PSTR), (line 35). I'm not really sure why though.
Can someone help me with CI for Rust please. I have an old project that use Circle CI to build a desktop and wasm game. A good soul made some PR a few days ago which made the CI failed because Github changed the authorization scheme. I updated that and expected the CI to work again but now for some reason the web build now try to use a more recent version of rustc-demangle which failed to build on the nightly I use in the CI (2019-12-20). The weird thing is that the version pinned in the Cargo.lock specify the 0.1.16 version while the web build try to use the version 0.1.21. Any idea why this is happening?
Can someone help me with CI for Rust please. I have an old project that use Circle CI to build a desktop and wasm game. A good soul made some PR a few days ago which made the CI failed because Github changed the authorization scheme. I updated that and expected the CI to work again but now for some reason the web build now try to use a more recent version of rustc-demangle which failed to build on the nightly I use in the CI (2019-12-20). The weird thing is that the version pinned in the Cargo.lock specify the 0.1.16 version while the web build try to use the version 0.1.21. Any idea why this is happening?
Thank you u/Darksonn! Looks like your https://github.com/tokio-rs/tokio/blob/master/.github/workflows/ci.yml is enough to get me started :)
I have uploaded a repository to Github with the issue.
Unfortunately I was not able to come up with a simple fix. I can however point you to the Bevy crate that includes code quite similar to yours so you can take a look how they solved the problem. The code is at https://github.com/bevyengine/bevy/blob/main/crates/bevy_wgpu/src/renderer/wgpu_render_context.rs. Look for the begin_pass function.
You can check https://github.com/ducaale/xh/blob/master/.github/workflows/release.yaml which runs some tests before releasing the CLI app for Windows, Linux and macOS
There's some discussion about turning off bundled in this issue: https://github.com/launchbadge/sqlx/issues/191