| 18 May 2022 |
 ngh | pls no | 18:30:09 |
 Levy | zip files sent by email with the current date as the version | 18:31:08 |
| ngh | Yes please | 18:32:18 |
| Levy | code sent within a Micro$oft word document | 18:33:28 |
| Levy | versioning is just incrementing a number at the end of the name | 18:34:55 |
 OJ | In reply to @tauoverpi:tchncs.de
versioning is just incrementing a number at the end of the name Like editing DNS or some database schemes. | 18:36:10 |
| Levy | Oh I mean
- stuff-1.docx
- stuff version 2.docx
- Stuff (version 3).docx
- stuff v 6.docx
| 18:37:05 |
 Michal_Atlas | okay, you won't believe what one of my classmates did in our introduction to git course
he did that, IN GIT
he literally just had a docv1.txt docv2.txt checked in and pushed to his repo | 18:56:27 |
| ngh | Beautiful | 18:58:22 |
 Daniel Peterson | https://xkcd.com/1459/ | 19:30:07 |
 jobotnik | In reply to @tauoverpi:tchncs.de
Tcll: At least try it before the C rewrite as Zig is meant to replace C here Zig isnt explicit and statically typed.... | 19:59:01 |
| jobotnik | In reply to @tauoverpi:tchncs.de
it's at least not as bad as java->scala Scala died because of too much complexity. Java is still alive and keeps growing | 19:59:59 |
| jobotnik | In reply to @lordmzte:mzte.de
my fav build system is cargo but zig is also awesome Nothing can replace tup (gittup.org/tup) | 20:03:41 |
| Levy | In reply to @jobotnik:matrix.org
Zig isnt explicit and statically typed.... > Zig isnt explicit
do go on, it's also statically typed which is nice
| 20:28:02 |
| jobotnik | Yes statically, but not explicit | 20:28:45 |
| Levy | compared to C there are far fewer implicit casts | 20:29:45 |
| Levy | you have quite a few pointer attributes which are tracked by the type system rather than having you guess at what they should be which is what happens in C | 20:30:28 |
| jobotnik | Hum? | 20:30:38 |
| Levy | the only implicit casts are safe pointer casts ([]u8 -> []const u8 and so on) and integer/float widening | 20:31:28 |
| Levy | and a few more https://ziglang.org/documentation/master/#Casting | 20:32:12 |
| Levy | see how anything which may lose information or result in an inexact value is handled with a builtin which you must call upon yourself | 20:33:23 |
| Levy | you cannot truncate without @truncate() or @intCast() (assert no bits are lost), integer overflow is caught unless you specify the behaviour on overflow with either modular or saturating arithmetic operators | 20:36:00 |
| jobotnik | Interesting | 20:37:09 |
| Levy | so whenever there isn't an obvious correct choice, the language forces you to make one | 20:37:30 |
|  californiatoke joined the room. | 20:37:39 |
| Levy | even division on integers requires a choice in truncation behaviour | 20:37:42 |
| Levy | https://ziglang.org/documentation/master/#divExact | 20:38:20 |
| Levy | so I'd say zig is certainly more explicit than C when it comes to types, operators, pointers, and casts | 20:39:31 |
|  sunzu joined the room. | 21:27:32 |
|  mendykin joined the room. | 22:26:49 |
