mesonbuild/meson

Recommend a standard coding style for meson.build files

Open

#2,608 建立於 2017年11月11日

在 GitHub 查看
 (8 留言) (5 反應) (0 負責人)Python (4,978 star) (1,465 fork)batch import
documentationenhancementhelp wanted

描述

It seems that there is no recommended standard for the coding style of meson.build files.

So in some projects the indentation is with two spaces, in other projects it's with tabs or four spaces, etc etc.

I think it's useful to have the same coding style in all projects, it makes contributing easier, it is also easier to copy/paste a snippet of code between projects.

Like the PEP 8 for Python: https://www.python.org/dev/peps/pep-0008/

貢獻者指南

技術棧
python
領域
documentationdeveloper experience
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
Review the existing comments in issue #2608 for prior suggestions and arguments. Examine style examples from other Meson projects (e.g., GNOME, GStreamer) and open source style guides like PEP 8. Propose a specific style guide (e.g., 4 space indentation, consistent quoting) and add it as a new documentation page in the Meson manual. Submit a pull request with the proposed style and rationale.
Recommend a standard coding style for meson.build files · mesonbuild/meson#2608 | Good First Issue