My copy of the Zigling exercises and their solutions. See the original at https://codeberg.org/ziglings/exercises https://git.muftee.net/zigling-exercises.git/atom?h=main 2021-03-12T23:59:46Z 2021-03-12T23:59:46Z Dave Gauer dave@ratfactor.com 2021-03-12T23:59:46Z urn:sha1:0956f1839fcaaa273353148da9e157a8f9690d2f When I hit 999 exercises, I will finally have reached the ultimate state of soteriological release and no more exercises will be needed. The cycle will be complete. All that will be left is perfect quietude, freedom, and highest happiness. 2021-02-28T18:23:22Z Dave Gauer dave@ratfactor.com 2021-02-28T18:23:22Z urn:sha1:5f7e9389d5a8d5829f9a7a7fe50153e3d82abf7f 2021-02-28T16:27:13Z Dave Gauer dave@ratfactor.com 2021-02-28T16:27:13Z urn:sha1:594a5c0f473e72bff7380991e103373cb2dc489d 2021-02-28T16:00:20Z Dave Gauer dave@ratfactor.com 2021-02-28T16:00:20Z urn:sha1:077a779f3d2fdfc03b2108c518cde2e6d4133ead It was confusing to see tail... = undefined in the struct definition and then if (tail == null) later in the exercise - it appears that the mismatch would be the issue - but that's distracting from the real issue: making the value optional! Changing the initial value to null is still correct, but won't distract. The only worry now is that the user will remember the undefined definition from the previous exercise and wonder if that has to be that way...but you can't win them all! 2021-02-17T01:21:32Z Dave Gauer dave@ratfactor.com 2021-02-17T01:21:32Z urn:sha1:f27601b55825fd8037082338ae996585946ef408