Add integrity check for owner relationships

[vinistock]

Note: this PR starts running resolution on our top 100 gems check, which fails until #505 is shipped.

This PR adds an integrity check back, so that we can perform more expensive validation of the graph to catch bugs early.

This first iteration only validates ownership relations. The implemented rules are:

• Only Object and BasicObject can own themselves
• All owners are namespaces
• All singleton classes are eventually attached to a namespace that isn't a singleton class (which would create infinite recursion in certain parts of the algorithms)

I exposed this API to Ruby, so that we can start running it against the top 100 gems.

[vinistock]

• Include RBS paths when indexing workspace #609
• Add integrity check for owner relationships #592 👈 (View in Graphite)
• Avoid creating singleton classes for non-namespace targets #623
• Auto promote when creating constants inside namespace #622
• Fix corner cases of re-opening aliases #621
• Follow aliases when they are used in mixins or parent classes #620
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[st0012]

We should rename error.rb as well. Otherwise looks good

[vinistock]

Merge activity

• Mar 4, 9:15 PM UTC: @vinistock merged this pull request with Graphite.