Time constraint

[maxitg]

Changes

• PostTagSearcher now correctly uses the time constraint parameter.
• ConclusionReason will either be TimeConstraintExceeded or NotEvaluated based on whether the time constraint was reached before or during the evaluation of a particular init.

Comments

• Checkpoints Searcher checkpoints #21 should be merged first.
• The time constraint will be exceeded slightly because results need to be collected.

Examples

• The first result of the following concludes with reason TimeConstraintExceeded:

PostTagSearcher::EvaluationParameters parameters;
parameters.groupTimeConstraintNs = 100000000;  // 0.1 seconds
const auto result = PostTagSearcher().evaluateRange(
    64, 1473593303835332608, 1473593303835332609, parameters);

• The other two results are NotEvaluated for now, but that can change after parallelization is implemented.

---

This change is 

[okofish]

Would you be able to add an option (e.g. an EvaluationParameters member) that causes NotEvaluated results to be omitted entirely from the output? Since the EvaluationResult includes the initial state and I subsequently include that state in each result file entry, for the purpose of generating a result file there's no utility in including NotEvaluated results.

[maxitg]

@okofish, sure, I'll do that.

[maxitg]

@okofish, sure, I'll do that.

Done.

[okofish]

Oh no, now we can only run for 292 years instead of 584!