Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Mi 10.07.2024 00:00:00 39.348 +2 1.420.452 36,1 ohai.social 4.3.0... 500 Di 09.07.2024 00:00:25 39.346 +3 1.418.682 36,1 ohai.social 4.3.0... 500 Mo 08.07.2024 00:02:18 39.343 +3 1.417.031 36,0 ohai.social 4.3.0... 500 So 07.07.2024 00:00:09 39.340 +2 1.414.815 36,0 ohai.social 4.3.0... 500 Sa 06.07.2024 00:01:02 39.338 +1 1.413.445 35,9 ohai.social 4.3.0... 500 Fr 05.07.2024 00:02:35 39.337 +1 1.411.622 35,9 ohai.social 4.3.0... 500 Do 04.07.2024 00:00:20 39.336 -1 1.409.903 35,8 ohai.social 4.3.0... 500 Mi 03.07.2024 00:03:14 39.337 +1 1.408.300 35,8 ohai.social 4.3.0... 500 Di 02.07.2024 00:04:01 39.336 0 1.406.815 35,8 ohai.social 4.3.0... 500 Mo 01.07.2024 00:02:09 39.336 0 1.405.321 35,7 ohai.social 4.3.0... 500
Martin Geisler (@mgeisler) · 11/2023 · Tröts: 219 · Folger: 161
Mi 10.07.2024 11:20
I cannot read it, but I love how the Ukrainian translation show-cases the #Unicode support of Rust string literals: https://google.github.io/comprehensive-rust/uk/concurrency/channels/unbounded.html
I know most programming languages support this today, but I rarely see it because most code I touch is written fully in English.
The Japanese translation uses English strings in the code, and that's okay too — our translation infrastructure gives teams the option of translating string literals, but we don't require it.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Elk