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

[RFC] Reserving aliases for unsigned `Fixed` and signed `Normed`

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

首先阅读 #199 中之前的讨论以及相关的命名 issue #51,然后将为 unsigned Fixed 和 signed Normed 提议的别名与现有的别名约定进行比较。命名选择和迁移方向得到解决即视为完成;此 issue 不确定实现文件或测试。

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

描述

doc

As noted in #199, unsigned Fixed and signed Normed are mathematically definable, but we still have some preparations to implement them.

Although those types are certainly not used often, but in fact, I occasionally use unsigned Fixed in private projects. In that case, I give those types redundant names.

However, when we handle concrete Fixed/Normed numbers, we often use the aliases (e.g., Q0f7, N0f8). If we have the predetermined aliases for unsigned Fixed and signed Normed, they can be used to make the future migration easier.

See also #51

Candidates

unsigned Fixed
  • UQxfy (Unsigned Q)
  • Qxfy (x+y == 8sizeof(T))
  • Uxfy (Unsigned)
  • Rxfy (following Q)
  • Fxfy (Fixed)
  • Xxfy (fiXed)
signed Normed
  • SNxfy (Signed N)
  • Nxfy (1+x+y == 8sizeof(T))
  • Sxfy (Signed. cf. #143)
  • Mxfy (norMed. followed by N)

Renaming Nxfy to UNxfy is a consistent practice, but it defeats the purpose of making the migration easier.

主要语言
Julia
星标
95
派生
38
平均合并
16 小时 31 分钟
30 天内合并 PR
9

环境准备

从这里开始

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

JuliaMath/FixedPointNumbers.jl 的其他 Issue

查看 JuliaMath/FixedPointNumbers.jl 的全部 Issue

相似的 Issue

更多 Julia Issue

把新 issue 发到你的邮箱

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