Read and process file line by line

[petricavalry]

Rewrite signature counter.

Some Specific Rules

Signature count was considered zero when missing signature block.

Learn more rules from unit tests.

Breaking Changes

HTML comments should be placed on standalone lines.

Ok:

<!-- BEGIN LGBT-CN SIGNATURE -->
<!-- END LGBT-CN SIGNATURE -->

<!-- BEGIN LGBT-CN COUNT -->
<!-- END LGBT-CN COUNT -->

Wrong:

<!-- BEGIN LGBT-CN SIGNATURE --><!-- END LGBT-CN SIGNATURE -->
<!-- BEGIN LGBT-CN COUNT --><!-- END LGBT-CN COUNT -->

Thanks for all amazing work in LGBTQIA In China.

Feel free to adjust any part of this pull request.

[KevinZonda]

Hi, thank you for your PR. The LGBT-CN SC is designed for a trust box rather than a black box, i.e., we have 2 foundamental assumptions:

• begin's index < end's index (guaranteeded by CR)
• low amount data (i.e., the whole data we proccess can fit into the main memory, in other words, work w/o buffer reader is acceptable)

If you dont mind, please explain what this PR can improve, this will help. Thanks again for your PR.

[petricavalry]

Thanks for your review. I am happy to draft this pull request.

You are right. I have include unnecessary checks and use an unnecessary buffer. It may work better without these changes.

I reviewed the commit history and I have a question: Why did you rewrite the signature-counter (Rust) in Go?

[KevinZonda]

I am not familiar with Rust. We met an unexpected behaviour with the previous SC (Signature Counter), and I cannot debug the programme with 瞪眼法. So we decided to convert it to Go with a much reliable approach (reliable means if not works, it will panic or broken, which will fail the CI).

[KevinZonda]

I will draft this PR for a while. I'll rethink this PR when Im free.