Fix the following error when running tests with go 1.24:
lib/iterator/iterator_test.go:58:12: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:62:13: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:66:12: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:69:12: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:83:12: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:87:13: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:91:12: non-constant format string in call to (*testing.common).Errorf
lib/iterator/iterator_test.go:94:12: non-constant format string in call to (*testing.common).Errorf
Signed-off-by: Robin Jarry <robin@jarry.cc>
Add a new models.UID type (an alias to string). Replace all occurrences
of uint32 being used as message UID or thread UID with models.UID.
Update all workers to only expose models.UID values and deal with the
conversion internally. Only IMAP needs to convert these to uint32. All
other backends already use plain strings as message identifiers, in
which case no conversion is even needed.
The directory tree implementation needed to be heavily refactored in
order to accommodate thread UID not being usable as a list index.
Signed-off-by: Robin Jarry <robin@jarry.cc>
Tested-by: Inwit <inwit@sindominio.net>
Tested-by: Tim Culverhouse <tim@timculverhouse.com>
Simplify the index handling for moving to the next or previous message.
Same for moving to the next or previous search results. Moving of the
index variable relies on the iterator package's StartIndex and EndIndex
functions.
Signed-off-by: Koni Marti <koni.marti@gmail.com>
Acked-by: Robin Jarry <robin@jarry.cc>
Extract the index acrobatics from the message store and move it to
iterator package for re-use and to add unit tests.
Signed-off-by: Koni Marti <koni.marti@gmail.com>
Acked-by: Robin Jarry <robin@jarry.cc>
Implement an iterator framework for uid and thread data. Iterators
ensure that the underlying data is accessed in the right order and
provide an abstraction of the index handling.
Iterators should be used when the order of the uids/threads is
important.
Signed-off-by: Koni Marti <koni.marti@gmail.com>
Acked-by: Robin Jarry <robin@jarry.cc>
