Flatpak runtimes aren’t part of atomic updates.
Flatpak runtimes aren’t part of atomic updates.
There are many furries in the open source community, but somehow I have never seen a penguin furry.
Edit: I forgot that penguins are birds, lol. Birds have feathers, not fur.
Edit²: Avians/featheries seem to be a thing: https://en.wikifur.com/wiki/Avian
That’s just brilliant.
To be fair, these alternatives are also limited to the case where the item type stays the same.
map()
can still be used with Vec::iter_mut()
, filter_map()
can be replaced with Vec::retain_mut()
.
I think the better solution would be to use Vec::retain()
.
Tl;dr: std::process::Command
is vulnerable to shell injection if you invoke cmd.exe
or *.{cmd,bat}
on Windows.
Good to know which community to avoid if I ever get into Tiling WMs
Does “cross platform apps” include Windows in your case? If so, how is your experience compiling and packaging a libadwaita app for Windows?
Thanks for coming back to this!