Problem

Currently, signature testing is conducted by rbs/unit_test. However, there are the following issues:

• Many methods exist that have not been tested.
• There is a pattern that has not been tested.
• It takes time to cover the pattern.

Solution: RaaP

raap is a testing tool for RBS signature. RaaP can materialize objects and execute methods as long as there is an RBS signature, and it can verify whether the return type matches.

The effectiveness of RaaP can be explained by this PR.

Take Set as an example

This PR covers Set. Many of the Set signatures have not been tested and RaaP has been able to find some errors. The ability to verify many test cases without writing test code is one of the advantages of using RaaP.

I removed Object & and made adjustments to minimize changes.

I removed Object & and made adjustments to minimize changes.

🆙. Non critical changes to the RBS are better scoped for another PR (or after some adjustments to the .rb itself)