rigor-builtin-import

Importing Ruby built-in class types requires incorporating CRuby reference source files and RBS signatures to regenerate catalog YAML data. This process updates the catalog to reflect new or updated class definitions for accurate type inference across your projects.

Ruby type inference fails for core classes like Hash and Time when the static analysis catalog lacks their built-in method types. Importing these types from CRuby reference sources into the catalog extends coverage and enables accurate type reasoning and bug detection.

Adding Ruby core class types to a static analysis catalog requires source files, RBS signatures, and the regeneration of catalog YAML data. You must also update runtime loaders to reflect the newly imported or refined class definitions.

Yes, you can use RBS signatures to update Ruby static analysis catalog YAML files. By incorporating the RBS signatures alongside CRuby reference source files, you can regenerate the catalog data to support improved type inference for built-in classes.

When importing Ruby stdlib types for type inference, you handle mutations through decision points during catalog data regeneration. This classification process ensures accurate type reasoning when extending per-class catalog coverage for stdlib classes like Set and Range.