



3



Run on join
== Éxécuter en joignant
not better to put " Executer en rejoient ? (edited)










zlib-sys to flate 2 with the zlib backend, and for wasm flate 2 with the rust-native backend
https://doc.rust-lang.org/reference/conditional-compilation.html
^ this leads me to believe my dependencies should look smth like this:
[target.'cfg(target_family = "wasm")'.dependencies]
flate2 = { version = "1.0.17", features = ["rust_backend"] }
[target.'cfg(not(target_family = "wasm"))'.dependencies]
flate2 = { version = "1.0.17", features = ["zlib"] }
However, this apparently isn't it yet. However my observations while fiddling around a bit seem so damn contradictive that I wanted to see if you might have an idea:
with the configuration above, both the wasm and non-wasm build use the zlib backend
if I remove the first two lines, the wasm build fails due to flate2 being an undeclared crate or module and the non-wasm build succeeds
If I change the zlib to rust_backend in the bottom two lines both wasm and non-wasm builds use the rust_backend




Show quads
== Afficher les quads quads ?













git submodule update returns nothing.
git status returns:






windows cmd needs double enter to start command
1












































































wget -O data/countryflags/AD.png https://zillyhuhn.com/cs/.1647976588.png














Found no clang-format 10





































file






src/base/unicode/tolower.cpp and the other is defined in <cctype> and i didn't know this was possible, but linker is actually using the array as a fucking function...