RFC: Reorganize module namespaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- vim
- Domain
- tooling
Research direction
Start by reviewing the linked Google spreadsheet and the discussion in vim-jp/#vital-dev, then read related issues #376 and #423. The issue needs an agreed namespace policy before implementation can begin; done would include the decided module reorganization and the proposed package rules documented in the README.
Written by the indexing model from the issue text.
Description
Slack の vim-jp/#vital-dev にて、各モジュールがどのパッケージに入っているべきかの見直しの話題が出ました。
https://docs.google.com/spreadsheets/d/1ncrq_k64viFgR5bwpMf8IuYcDaiXjLx-2kNCoqQBvxs/edit
パッケージの現状を上記のスプレッドシートに軽くまとめ、見直しとして、以下のような意見があります。
Prelude.is_windows()系の関数をどこかに移したいSystemと言う名前割と曖昧なので用途をはっきりさせたい- 実行環境的なニュアンスがある
- その観点で言うと
System.Cacheだけ異端
Dataは Haskell から来ている- 方針決めて新しいモジュールセットを作りたい
ProcessとSystem.Processがあるのがわかりづらい- Process系全部廃止したい
- DateTime がひょこんと root にいるのもちょっと気になる
- どこに入れるべきか悩んだ結果そうなった
- パッケージごとに何に関するモジュールを入れとけばいいかってのだけ決めとけばいいのではないか
- ルールから逸脱するのだけはダメという感じ
- README とかに書いておきたい
- たたき台 https://docs.google.com/spreadsheets/d/1ncrq_k64viFgR5bwpMf8IuYcDaiXjLx-2kNCoqQBvxs/edit
- Data はデータ構造を突っ込む場所って観点だと思ったよりそんなに違和感あるモジュールはなかった
- データ構造と、
Data.Stringみたいに既存データを扱うやつが混在している
- データ構造と、
- System -> OS にしたい
is_windows系の移住先としてはOS使いたい- そもそも System って単語が幅が広過ぎる
Slack ではログが流れるため、ある程度の議論が終わったらこちらに dump してください。
関連 issue #376 #423
- Dominant language
- Vim Script
- Stars
- 586
- Forks
- 64
- Avg merge
- 9h 24m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vim-jp/vital.vim
-
Web.HTTP の非同期実行を行いたいPossibly taken @mikoto2000 claimed this 308 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Fix and feature: Add python setup in Github workflowMay be free again @tsuyoshicho claimed this 904 days ago, and no pull request is open. Open
-
Vim9.x: support change Vim 8.2/9.0 to Vim 9.0/9.1May be free again @tsuyoshicho claimed this 955 days ago, and no pull request is open. Open
-
feat: Bitwise.vim: bitwise shift operatorMay be free again @tsuyoshicho claimed this 1579 days ago, and no pull request is open. Open
-
Data.List: Deprecate function in string formMay be free again @ujihisa claimed this 2138 days ago, and no pull request is open. Open
All issues in vim-jp/vital.vim
Similar issues
-
stage-fail
Difficulty 1/5 Under an hour Newbie friendliness 72/100
siyuan-note/bazaar#2405 ·
Maintainers usually reply within 1 day
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --displayPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pingdotgg/t3code#24900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jrblevin/markdown-mode#960 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel-labs/agent-skills#348 ·
-
Codex теряет MCP-инструменты выбранного харнеса до завершения инициализацииPossibly taken @VictorMurashkin claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zeegin/1c-agent-exam-benchmark#22 ·
Maintainers usually reply within 1 day