Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Default to version: "current" instead of version: "latest" for Prism 2.0?

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
ruby
领域
compilers

调研方向

Start with the linked Ruby bug discussion and the existing Prism version option behavior. Assess the compatibility consequence described here—raising when Prism lacks a parser for RUBY_VERSION—and whether defaulting to "current" is appropriate for Prism 2.0; done means the default and its consequences are clearly decided.

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

描述

Coming from https://bugs.ruby-lang.org/issues/22379#note-13 and previous discussions on this topic, I think it would be more intuitive and less error-prone for most Prism users for the default version to be "current" and not "latest".

Another POV, if there was no default for the version, would there be more people specifying "current" or "latest"? I suspect more for "current" and "latest" would actually be pretty rare. I think most Prism use cases want either "current"/"nearest" or a fixed version, and rarely "latest".

Is that something that could be considered for the upcoming Prism 2.0?

Known consequences:

  • It will raise an exception if Prism doesn't have a parser for RUBY_VERSION. I think this is fine, and make people think about the right solution (update to a newer Prism, run on a newer Ruby, use "latest"/"nearest" knowing it won't be the exact grammar, etc).
主要语言
C
星标
1k
派生
195
平均合并
1 天 7 小时
30 天内合并 PR
21

环境准备

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

从这里开始

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

ruby/prism 的其他 Issue

查看 ruby/prism 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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