Expand Unit Test

[johnpatek]

The project currently has a single unit test that covers a few basic use cases, but it lacks comprehensive testing of the public API, and does not provide granular feedback through ctest when tests fail. The unit test should be refactored and reorganized to make better use of ctest, and should at least create a starting point for a comprehensive test of the entire API.

[wissem01chiha]

Hi @johnpatek, I’ve started working on mio., documentation generation and publishing are set up here: mio-docs.

Updates

• tests cleaned up using doctest (I usually use GoogleTest, but wanted to keep this lightweight).
• cmake cleanups: modularized only in subdirs with source files, not header‑only dirs.
• added and applied a .clang-format (LLVM‑based; feel free to suggest changes).
• new tools folder for automation scripts (linters, testing, coverage).
  • Long‑term: i am considering Codecov or Coveralls integration.
• benchmarks planned as time allows.
• I’ll open some pull request as changes are ready.

would you be open to proposing a project logo? , that will be very helpful, since i am planning to modernize the old doxygen style/layout.

I’d like to evolve mio into a lightweight lazy_loader library for efficient large‑file processing without loading the entire file into memory. Planned features include:

• parallel search: use C++11 threads to assign memory‑mapped chunks to different threads for find/insert/delete operations.
• index‑based access: build an index during the first parse so repeated lookups jump directly to the right memory page.
  • This will be developed in a separate feature branch and tested for thread safety.

[johnpatek]

Hi @johnpatek, I’ve started working on mio., documentation generation and publishing are set up here: mio-docs.

Updates

• tests cleaned up using doctest (I usually use GoogleTest, but wanted to keep this lightweight).

• cmake cleanups: modularized only in subdirs with source files, not header‑only dirs.

• added and applied a .clang-format (LLVM‑based; feel free to suggest changes).

• new tools folder for automation scripts (linters, testing, coverage).

  • Long‑term: i am considering Codecov or Coveralls integration.

• benchmarks planned as time allows.

• I’ll open some pull request as changes are ready.

would you be open to proposing a project logo? , that will be very helpful, since i am planning to modernize the old doxygen style/layout.

I’d like to evolve mio into a lightweight lazy_loader library for efficient large‑file processing without loading the entire file into memory. Planned features include:

• parallel search: use C++11 threads to assign memory‑mapped chunks to different threads for find/insert/delete operations.

• index‑based access: build an index during the first parse so repeated lookups jump directly to the right memory page.

  • This will be developed in a separate feature branch and tested for thread safety.

@wissem01chiha thank you for working on this, I have invited you via email to be a collaborator in this repository. As for the specifics:

• I am fine with the switch to doctest, clang-format, and codecov. I can configure this repo to link to our codecov account when it is time to do that.
• I can get someone working on the project logo, unless you already had one in mind. Just let me know.
• I like the idea of a lazy loader with enhanced searching, but I would like to know more of the details regarding whether this is baked into the entire implementation, or if it can be configured based on user needs. My main concern is backward compatibility, but I am open to breaking that if we are offering a significantly better product.

Either way, please carry on, and thanks again for your efforts.

[johnpatek]

@wissem01chiha I have assigned this issue to you. You should be able to create a branch and open PRs directly in this repo now.

[johnpatek]

Closing for now since #13 covered a lot of this.