Status of project
未關閉
還沒有人認領這個 Issue。
- 主要語言
- Makefile
- 星號
- 1
- 分支
- 1
- PR 合併指標
- 30 天內沒有已合併 PR
描述
I see great value to cpp-cli-skel because:
- Command line interfaces are a great way to prototype new projects
- Command line interfaces are a common and very valuable way to distribute C++ code, and therefore establishing best practices for how Mapbox devs develop C++ CLI interfaces is important for scaling our work.
At the same time this project has been dormant, in my mind, because:
- Attention of @mapbox/core-tech has so far been primarily on https://github.com/mapbox/hpp-skel
- https://github.com/mapbox/hpp-skel, because it contains benchmarks and unit tests executables, already has two types of "cli" examples, and therefore is fairly useful for using to prototype (no need for this separate cpp-cli-skel)
- Most serious command line tools end up needing to parse options, and option parsing in C++ requires an external dependency, which raises the harder question of which external dependency, refs https://github.com/mapbox/cpp/issues/35
Questions in my mind:
- Should we put this project on ICE and clearly direct interested people to hpp-skel for prototyping for now?
- Should we put time into investigating the ideal option parser and reboot https://github.com/mapbox/cpp-cli-skel/pull/2 with it and get things landed and working?
@mapbox/core-tech
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先檢視 hpp-skel 現有的 CLI 範例、mapbox/cpp#35 中尚未解決的 option-parser 討論,以及提議的 cpp-cli-skel#2 pull request。判斷此專案應該暫停還是重新啟動;完成的定義是維護者已選擇並記錄明確的方向。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- cpp
- 領域
- cli
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 20/100