mesonbuild/meson

Recommend a standard coding style for meson.build files

Open

#2608 opened on Nov 11, 2017

View on GitHub
 (8 comments) (5 reactions) (0 assignees)Python (4,978 stars) (1,465 forks)batch import
documentationenhancementhelp wanted

Description

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/

Contributor guide

Tech stack
python
Domain
documentationdeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
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.