Proposal to deprecate prototype features

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
ruby
领域
tooling

调研方向

首先审查原型 rb、rbi 和 runtime 的实现与用法,以及所引用的 issue 和 pull request。检查 Ripper、RubyVM::AbstractSyntaxTree 和 rbs-inline 与这些功能的关系。完成标准是就 rbs v4 的 deprecation warning 计划和 v5 的移除计划达成一致,同时决定是否保留 runtime 供 core 和 stdlib 内部使用。

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

描述

RBS has 3 prototype features. I propose to stop maintaining all of them and eventually deprecate them.

Issues

Implementation as Experimental Features

All three prototypes (rb, rbi, runtime) use Ripper or RubyVM::AbstractSyntaxTree.

Both Ripper and RubyVM::AbstractSyntaxTree are experimental features, and their deprecation has also been proposed.

Decreasing Use Cases

rb

The rbs-inline gem almost entirely covers the prototype rb functionality and is planned to be integrated into the rbs repo in rbs v4. It is expected that prototype rb will no longer be used.

rbi

The rbi feature has served its purpose and is likely no longer in use.

runtime

The runtime feature lacks sufficient functionality for use in large-scale codebases like applications, and for simple use cases, rbs-inline is often sufficient.

Deprecation Method

I propose to issue a warning for prototype features starting with rbs v4, indicating they are slated for deprecation, and to completely remove them in v5.

The runtime feature may still have uses for expanding type definitions in core and stdlib, so it is highly likely to remain for internal use within the rbs repository.

Refs

主要语言
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 摘要。