Neptune-Crypto / neptune-core / 17548593754

75%

push

github

Merge PR #691: Revise Directory Structure

# Summary of Changes

 - (Attempt to) put `benches/` and `benchmarks/` into common parent directory benchmark. Unfortunately, this change can only be applied half-way because it relies on a matching change in tasm-lib to unhardcode the name of the directory where benchmark reports are stored. The part of the change that was applied was moving `benches/` to `benchmark/benches/`. Moving `benchmarks/` to `benchmark/reports/` will have to wait for a future commit.
 - Rename `models/` to `protocol/` and `models/blockchain/` to `protocol/consensus/`.
 - Move `models/state/` out one level. Directory `state/` is now on par with `protocol/`.
 - Create directory `application/`, on par with `protocol/` and `state/`. Directory `application/` now contains:     
   - `config_models/`, which has, incidentally, been renamed to `config/`
   - `database/`
   - `job_queue/` and `triton_vm_job_queue/`
   - `locks/`
   - `loops/` which, in turn, now contains main_loop/, mine_loop/, and peer_loop/
    - `rpc/`
 - Add directory `state/mining/` and move files related to mining state there.
 - Add directory `state/transaction/` and move files related to state and transactions there.
 - Move a couple of individual files to better fitting directories.

# Categories

## Application

"Application" is conceived of as this particular application as well as utilities that help this particular application work smoothly. It makes abstraction (to the maximum possible extent) of the particular blockchain protocol that it is an application for; and also of the logic for replicating the state in order to sync to that blockchain network. Conceivably, you could swap out the archival state for a sparse state, or for a state that lives entirely in RAM, and very little would change in the application module. Likewise, you could conceive of changes that dramatically affect the blockchain protocol, such as a hard fork, that bring about next to no change... (continued)

119 of 186 new or added lines in 38 files covered. (63.98%)

24412 of 32880 relevant lines covered (74.25%)

650555.34 hits per line