-
Example "clock" crashes on macOS 11.1 with `[1] 6987 segmentation fault cargo run --package clock`. Backtrace generated using `rust-lldb target/debug/clock`. Seems like a problem with `Metal`.
``…
-
I cannot see way to resolve this error that refer to this line https://github.com/dancespiele/okspiel/blob/master/src/connect/connect_node.rs#L384 . Compile throw this:
```rust
cannot infer an app…
-
With its optional tokio 0.3 dependency, iced is in an awkward position where if you want to use those features, iced is incompatible with many other crates that skipped tokio 0.3 and moved directly fr…
fenhl updated
3 years ago
-
# Can't run minimal example : panics immediately
I tried running the example provided but it panics immediately with
`thread 'main' panicked at 'called "Result::unwrap()" on an "Err" value: State…
-
I couldn't build hypervisor package and get the error below. First error is related to x86_64 module in hypervisor module. I don't know where x86_64 crate comes from because I'm new to cloud-visor. I …
-
With the recent addition of error handling, I tried to wrap an iced::Result with an anyhow::Result, but it's not working because I get this error:
```
error[E0277]: `(dyn StdError + 'static)` cann…
-
Similar to #23: bddisasm decodes `64666526490f3f` as `PFRSQRTV mm2, mm7` when in 64-bit mode, despite being a 16/32-bit only instruction on some very old AMD Geode CPUs:
64410f0fd787 | (0 / 0) | …
-
bddisasm currently decodes `4ddfe1` as `FSTDW`.
`FSTDW` is a floating point instruction that only existed on the 80387SL. As such, no modern AMD64 CPU supports it, and it can only ever possibly be …
-
I get this error:
```
thread 'tokio-runtime-worker' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /home/spielrs/.cargo/registry/src/github.com-1e…
-
How do you make an image button?
When I try
```rust
iced::Button::new(
&mut state,
iced::Image::new("a/path/img.svg"),
)
```
... it doesn't compile:
```rust
error[E0277]: the…