Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Sa 05.10.2024 00:00:05 62.144 +1 3.764.649 60,6 Fosstodon 4.2.13 500 Fr 04.10.2024 00:00:07 62.143 +3 3.762.219 60,5 Fosstodon 4.2.13 500 Do 03.10.2024 00:00:23 62.140 0 3.759.060 60,5 Fosstodon 4.2.13 500 Mi 02.10.2024 00:00:06 62.140 +1 3.755.928 60,4 Fosstodon 4.2.13 500 Di 01.10.2024 00:01:13 62.139 +1 3.752.620 60,4 Fosstodon 4.2.13 500 Mo 30.09.2024 00:01:12 62.138 +3 3.749.484 60,3 Fosstodon 4.2.12 500 So 29.09.2024 00:01:07 62.135 -1 3.746.995 60,3 Fosstodon 4.2.12 500 Sa 28.09.2024 00:01:07 62.136 +2 3.745.047 60,3 Fosstodon 4.2.12 500 Fr 27.09.2024 00:01:07 62.134 +2 3.741.982 60,2 Fosstodon 4.2.12 500 Do 26.09.2024 00:00:18 62.132 0 3.738.514 60,2 Fosstodon 4.2.12 500
(@mort) · 05/2019 · Tröts: 1.784 · Folger: 184
Sa 05.10.2024 11:35
Do you prefer languages where struct initializers must follow declaration order (such as C++ aggregate initialization with designated initializers) or languages where initialization order can differ from declaration order (e.g Rust, where I can init a 'struct X { a: int, b: int }' with 'X{b: 10, a: 20}')
I kinda like when initialization order must follow because I hate accidental inconsistency, that's my bias at the outset, but I wanna see if I'm alone in that
Prefer init and declaration must be the same order (0)
Prefer when initialization order may differ (0)
2024-10-08T09:35:33.899Z
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0