3 ms·
My understanding of the Zig's team's opinion is that Zig is not currently at a place where they want to solidify the design by doing such things as writing exte
by llimllib 5y ago
My understanding of the Zig's team's opinion is that Zig is not currently at a place where they want to solidify the design by doing such things as writing extensive tutorials documenting how to write it - tutorials that will need to be updated every time they make breaking changes, which they explicitly still want to do.
A lot of this seems to be a mismatch between people's expectations of zig's stability and the reality?
- snek_case 5y agoThe way you handle that is by adding all your tutorials to the test of tests for the compiler. Then, whenever a breaking change happens, you have to update the tutorials for the tests to pass, which isn't difficult since you're probably only talking about minor, incremental changes.
- all2 5y agoI like this idea quite a lot. If you can write the tutorial itself in a "literate code" sort of way, the test harness should be able to consume the entire tutorial and run tests against it. Presuming, of course, that there's a way to tangle/weave using standard comments in Zig. Sounds like it could be a fun project. Could also serve as a way to auto-doc (like JavaDocs or similar using documentation generators).
- AnIdiotOnTheNet 5y agoZig already does this with its current documentation and example code.