![](https://lemmy.keychat.org/pictrs/image/1f08ce6b-6c40-4066-b51c-7abb6cdc5ad6.jpeg)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
I’d usually do the former because by build number I usually mean pipeline or job id in a build server. You could build 4.0.4 and then 3.4.18 and so 4.0.4 could be build number 1026 while 3.4.18 is 1027.
You can also just use a special number to keep your version number unique when doing dev builds so your version number comes through like 3.5.2-48 and some might call the 48 a build number, in which case that would make sense to reset with each version number.
Seems kinda trash tbh. Like the concept I love, I would love a cross-language “by examples” learning resource and snippet repository beyond SO. But looking through there most of the function options are trivial problems. The ones that aren’t one or two lines mostly have broken code that passes very few tests. The weird Z naming of function and variable makes it totally unreadable. The “composition” option is barely comprehendable and beyond that I only see two language options so it can’t even serve as a “rosetta stone”.