Ian Douglas Scott

And if you look at a file like https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/stable/linux-dmabuf/linux-dmabuf-v1.xml?ref_type=heads, you'll also see a copy of the MIT license. In the `` section.

Good catch. Presumably upstream wayland-protocols would like to fix that; and might benefit from some kind of CI check that would notice the `` section being missing.

And we can include the `COPYING` file too, really. It doesn't take up much space. But as far as I can tell, the intent upstream is that these files should...

I'm not familiar with OpenBangla, but Ibus currently doesn't work on cosmic-comp, since cosmic-comp currently only provides the input-method-v2 protocol, while ibus uses input-method-v1 (https://github.com/ibus/ibus/pull/2256). fcitx5 should work, but input...

So like the earlier backtrace, this is in `wl_map_insert_at`, called by `proxy_destroy`. But destroying a different object, and in Mesa instead of Nvidia's egl-wayland. So maybe not a driver bug....

> There are no such pins (and no DRAM) on the [sipeed_tang_nano_20k](https://github.com/litex-hub/litex-boards/blob/master/litex_boards/platforms/digilent_nexys_video.py), and the built-in assumption that there would be results in the error you're reporting. I don't think that...

Generally it can be awkward in Rust to deal with types that don't implement `Send` (i.e. they can't be safely moved between threads). Normally this trait applies, even for types...

https://learn.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformance lists `C11 threads ` as added in `VS 2022 17.8`. So I guess it's a relatively recent addition (compared to when C11 was standardized), but should be available.

Well, I could add an example, but it just amounts to `simple_window` but printing a message every frame. Not sure we need that.

I'm not sure there's a way to avoid some kind of redundancy here as long as `wayland_client` has a helper related to globals, and `sctk` needs a helper that provides...