CONTRIBUTING.rst: update for Rust

This commit is contained in:
David Adam 2024-11-06 23:27:04 +08:00
parent 7f29f09d25
commit 767ae87191

View file

@ -42,8 +42,8 @@ Guidelines
In short: In short:
- Be conservative in what you need (``C++11``, few dependencies) - Be conservative in what you need (keep to the agreed minimum supported Rust version, limit new dependencies)
- Use automated tools to help you (including ``make test``, ``build_tools/style.fish`` and ``make lint``) - Use automated tools to help you (including ``make test`` and ``build_tools/style.fish``)
Contributing completions Contributing completions
======================== ========================
@ -101,7 +101,7 @@ To ensure your changes conform to the style rules run
before committing your change. That will run our autoformatters: before committing your change. That will run our autoformatters:
- ``git-clang-format`` for c++ - ``rustfmt`` for Rust
- ``fish_indent`` (shipped with fish) for fish script - ``fish_indent`` (shipped with fish) for fish script
- ``black`` for python - ``black`` for python
@ -322,12 +322,12 @@ Setting Code Up For Translations
-------------------------------- --------------------------------
All non-debug messages output for user consumption should be marked for All non-debug messages output for user consumption should be marked for
translation. In C++, this requires the use of the ``_`` (underscore) translation. In Rust, this requires the use of the ``wgettext!`` or ``wgettext_fmt!``
macro: macros:
:: ::
streams.out.append_format(_(L"%ls: There are no jobs\n"), argv[0]); streams.out.append(wgettext_fmt!("%ls: There are no jobs\n", argv[0]));
All messages in fish script must be enclosed in single or double quote All messages in fish script must be enclosed in single or double quote
characters for our message extraction script to find them. characters for our message extraction script to find them.