Taiki Endo

All related issues have been closed, but is there still a problem with your use case?

(The MSRV policy for libc is currently being discussed in https://github.com/rust-lang/libs-team/issues/72)

(https://github.com/rust-lang/futures-rs/pull/2809 may or may not have fixed this.)

The fix is available at [taiki-e/vertex-index-32](https://github.com/openrr/urdf-viz/tree/taiki-e/vertex-index-32), but it depends on the unreleased change in kiss3d.

Yeah, for environments where ROS is not available, specifying the path or URL to the package with `--package-path` is the currently recommended way. https://github.com/openrr/urdf-viz?tab=readme-ov-file#how-to-use > If there are "package://" in...

- Since `task::{Context, Poll}` is also needed to implement `Future`, including `Future` in the prelude would be of little use from the standpoint of eliminating import effort during manual implementation....

I think that will work for private dependencies, but for public dependencies, I think one of the builds will break when both crate using `k` and `nalgebra` 0.31 and crate...

It does not seem to work as you said in https://github.com/openrr/k/pull/91#issuecomment-1375921174. For example, the following will cause a "mismatched types" error due to version mismatch: ```toml [package] name = "a"...

> `cargo clippy` sets `clippy-driver` as RUSTC_WRAPPER (Not related to this bug itself, but AFAIK, as said in https://github.com/cuviper/autocfg/issues/58#issuecomment-2067625980, `cargo clippy` sets `clippy-driver` as RUSTC_WORKSPACE_WRAPPER, not RUSTC_WRAPPER.)

I have a patch to support `#[async] for` and `#[async_stream]` in futures 0.3: https://github.com/rust-lang-nursery/futures-rs/compare/master...taiki-e:async-stream Currently, this is blocked in work for the futures_api stabilization (https://github.com/rust-lang-nursery/futures-rs/pull/1514), but after the futures 0.3.0-alpha.14...