From 3ed89cc2504bdd45ebe793e734a199172ab7bc7a Mon Sep 17 00:00:00 2001 From: ripytide Date: Mon, 5 Dec 2022 21:10:32 +0000 Subject: [PATCH] tidy todo.txt --- todo.txt | 34 ++++++++++++++-------------------- 1 file changed, 14 insertions(+), 20 deletions(-) diff --git a/todo.txt b/todo.txt index 3167879..61a5281 100644 --- a/todo.txt +++ b/todo.txt @@ -1,37 +1,31 @@ -- remove test is_valid_range_bounds and use the same one the module uses - -- write more mass tests for touches() - -- change all the tests to use map not set - -- write more tests for more complicated functions +# testing +- apply labels to crate and test #[untested]'s - test for atomnicity, if it fails it shouldn't affect the map -- write docs for undocced things - -- add issues to github for all the caveats -- review caveats again - -- copy map to set again - +# docs - write something somewhere about wrapper types for RangeBoundsMap that can simplify function signatures due to known invariants. For example a wrapper for using K=std::ops::Range which simplifies a LOT + probaly in caveats + github issue +- write docs for undocced things -- take a look around idiomatic rust for a bit first -- review method parameter names for all public functions - +# time based - use it in robot_Sweet_graph for a bit before publishing -#frequent -- update lines of code figures on docs +# final checks +- copy map to set again - copy readme to lib.rs docs again +- take a look around idiomatic rust for a bit first +- review method parameter names for all public functions +- update lines of code figures on docs +- add issues to github for all the caveats +- review caveats again - run and fix cargo clippy - PUBLISH +# after publish tasks - add links to [`RangeBoundsSet`] and map after docs.rs is live with the docs, and generally check for dead links on docs and readme - - tell people in issues of other rangemap libraries about my library stonks advertising