Proposal: Extend `ruby-rbs` crate features

未关闭
#2,954 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
ruby, rust
领域
devtools

调研方向

首先查看现有的 ruby-rbs crate 以及 rbs gem 中对应的上层。该提案涵盖 TypeName/Namespace、EnvironmentLoader、Environment 和 DefinitionBuilder,因此首先需要确定项目会接受哪个层次和范围。完成这项工作需要达成一致的 Rust 接口和实现计划,而不是进行一次孤立的单独修改。

由索引模型根据 Issue 内容生成。

描述

Motivation

The ruby-rbs crate currently provides only the parser layer (AST + Visit trait).
The rbs gem, in contrast, ships several higher-level layers on top of the parser — environment construction, name resolution, and definition (ancestor / method) resolution.

Until those layers exist on the Rust side, downstream tooling (type checkers, LSP servers, code generators) cannot be built using ruby-rbs alone. This issue proposes to gradually port those upper layers into the crate.

Features I want

I'm building a static type checker in Rust for my own gem.
Currently, RBS type definitions are loaded on the Ruby side and the result is then handed over to Rust for analysis.
I'd like to move the loading step into Rust as well, so the whole pipeline can be driven through a Rust interface — which requires the following layers in ruby-rbs:

  • TypeName / Namespace — structured type names like ::Foo::Bar; prerequisite for every layer below
  • EnvironmentLoader — discovering .rbs files from gem paths / libdirs, equivalent to rbs gem's loader
  • Environment — merging declarations from multiple files (class reopens, module aliases) and exposing a lookup API
  • DefinitionBuilder — resolving inherited methods via MRO so callers can ask "what methods does Foo::Bar expose?" without re-implementing ancestor traversal in every consumer

Of course, things won’t always go as planned.

Willingness to contribute

If the RBS core team is planning to expand ruby-rbs with these upper layers, I'd love to contribute actively — not just file this as a wishlist.

主要语言
Ruby
星标
2.2k
派生
263
平均合并
1 天 20 小时
30 天内合并 PR
64

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ruby/rbs 的其他 Issue

查看 ruby/rbs 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。