Taiki Endo

Results 173 issues of Taiki Endo

It might be nice with a section mentioning the often overlooked standard library APIs such as `Option::as_pin_mut` (e.g., https://twitter.com/fasterthanlime/status/1377229099622662146, https://github.com/hyperium/tonic/pull/1377, https://github.com/tower-rs/tower/pull/316#discussion_r319770004), `Pin::as_mut` (e.g., https://github.com/taiki-e/pin-project/issues/345), `Pin::set` (e.g., https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem/topic/.60Pin.60.20used.20for.20encapsulation/near/300322988, https://github.com/tower-rs/tower/pull/323#discussion_r322239400), etc., and...

C-documentation

Fixes #77 The visibility that has been parsed once by caller macro and can no longer be re-parsed by us (due to rustc bug) is forced to `pub(crate)`. Note: This...

breaking-change

Originally discussed in https://discord.com/channels/500028886025895936/627651185406509067/869996991105626152. > Well, it's fine to accept the newtype variant as a special case, if someone can implement it in pin-project-lite. Previous work by @Michael-J-Ward: https://github.com/taiki-e/pin-project-lite/pull/63, https://github.com/taiki-e/pin-project-lite/pull/68

C-enhancement
help wanted

### Summary It would be reasonable not to warn about code generated by external macros (macros defined in dependencies or standard libraries), since there is no way for the user...

C-bug
good-first-issue
I-false-negative

Fixes #355 See https://github.com/rust-fuzz/cargo-fuzz/issues/355#issuecomment-1974748776 and https://github.com/rust-fuzz/cargo-fuzz/issues/355#issuecomment-1974758107 for details. This PR uses the latter approach, which is more accurate. However, I have also [implemented the former approach in another branch](https://github.com/rust-fuzz/cargo-fuzz/compare/main...taiki-e:cargo-fuzz:default-target-no-dep) and...

Fix ui test failure on Rust 1.76: https://github.com/tokio-rs/async-stream/actions/runs/8127087685/job/22211533379

When used together with [setup-cross-toolchain-action](https://github.com/taiki-e/setup-cross-toolchain-action), we can easily get coverage of the target different from the host. It would be nice to document this in readme.

C-documentation

Related: https://github.com/NixOS/nixpkgs/pull/197478#issuecomment-1407563756

Remove the need for this one: https://github.com/openrr/openrr/blob/4c2fcb8e649dab5452889c32d56f4f286af33aec/arci/README.md#L14