-
Currently, all data calls are synchronous which could cause problems when things go wrong. Enable the ability to set an async callback in the native platform that is called from Rust with the required…
-
For example, here's the output of `cargo upgrade --incompatible=allow --pinned=allow`:
![Screenshot 2023-10-11 at 3 24 23 PM](https://github.com/killercup/cargo-edit/assets/225668/99269941-3e57-4a2…
-
This library seems quite nice, but it has a main downside compared to Rust code: The lack of early-return on errors.
Take this as an example:
```typescript
async fn read(path: string, key: stri…
dbrgn updated
2 years ago
-
### Code
```Rust
#![feature(impl_trait_in_fn_trait_return)]
use std::future::Future;
// ↓↓↓ remove this parameter and it works
fn f() -> impl Fn() -> impl Future {
|| async {}
}
``…
-
Stack trace:
```text
panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/syntect-5.2.0/src/parsing/regex.rs:70:53:
regex string should be pre-tested: ParseError(147, Inv…
-
auto-reduced (treereduce-rust):
````rust
struct Bug {
V1: [(); {
type F = impl core::future::Future;
fn concrete_use() -> F {
async { 1 }
}
…
-
I no longer think the benefits of having `Notify` as a separate trait are worth the trade-off, since in practice, most `Notify`s have a point where they could end. Additionally, when using pasts I ha…
-
My issue is that I want to return an empty tuple wrapped in a Result for a delete mutation. However, Rust panics that:
the trait bound `(): async_graphql::OutputType` is not satisfied
the followi…
-
Hello,
As the title says, async-redis-session is effectively dead, but it's recommended in the readme. There hasn't been activity on the repo since 2021, and not much heard from the author since 20…
-
While trying to debug #96734, I built LLVM with `-fsanitize=thread`, and virtually all ThinLTO tests failed with many dozens of TSan 'data race' errors, which looked very similar to this example:
`…