Remove stale TODO section references
Some checks are pending
libakstdlib CI Build / coverage (push) Waiting to run
libakstdlib CI Build / mutation_test (push) Waiting to run
libakstdlib CI Build / cmake_build (push) Successful in 2m55s
libakstdlib CI Build / sanitizers (push) Successful in 2m52s

This commit is contained in:
2026-08-03 13:21:15 -04:00
committed by Logikoma
parent 2b79aca103
commit a95ed6d13a
3 changed files with 5 additions and 6 deletions

View File

@@ -3,7 +3,7 @@
*
* Numeric conversion, complete. The cases that used to live in
* tests/test_convert_strict.c -- registered as a known failure because the ato*
* family had no error channel at all (2.1.5) -- are folded back in here now that
* family had no error channel at all -- are folded back in here now that
* they pass: non-numeric input, empty input, trailing junk and overflow are all
* errors rather than silent wrong answers.
*
@@ -54,7 +54,7 @@ static int test_atoi_rejects_null_arguments(void)
}
/*
* The whole reason 2.1.5 mattered. atoi("not a number") returned success and 0,
* The whole reason strict conversion matters. atoi("not a number") returned success and 0,
* so a caller could not tell a parse failure from a legitimate zero -- and
* akbasic had to write ~60 lines of its own strtoll/strtod wrapper to avoid
* turning four diagnosable BASIC errors into four wrong answers.

View File

@@ -4,8 +4,8 @@
* The two confirmed list defects are fixed, so the tests that used to live in
* tests/test_list_append_chain.c and tests/test_list_iterate_head.c are folded
* back in here: aksl_list_append builds the whole chain rather than truncating
* it at the midpoint (2.1.1), and aksl_list_iterate starts at the head rather
* than at whatever node Floyd's slow pointer happened to stop on (2.1.2).
* it at the midpoint, and aksl_list_iterate starts at the head rather than at
* whatever node Floyd's slow pointer happened to stop on.
*
* The chain assertions build their lists with aksl_list_append now, which is the
* point -- they could not, while append was the thing under suspicion.

View File

@@ -1,6 +1,5 @@
/*
* Memory wrappers, complete, plus the additions from
* section 3.1.
* Memory wrappers, complete.
*
* The three cases the wrapper plan left open are all pinned here: malloc(0) is AKERR_VALUE
* rather than whatever errno happened to hold when the platform's malloc(0)