Lines Matching +full:docs +full:- +full:openmp +full:- +full:html
12 inevitably be some details that are flawed. You can help - you can edit this
15 <http://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html>`_.
26 <../CodingStandards.html#name-types-functions-variables-and-enumerators-properly>`_
43 The proliferation of acronyms leads to hard-to-read code such as `this
44 <https://github.com/llvm/llvm-project/blob/0a8bc14ad7f3209fe702d18e250194cd90188596/llvm/lib/Transf…
61 This work-in-progress proposal is to change the coding standard for variable
65 …<https://github.com/llvm/llvm-project/blob/8b72080d4d7b13072f371712eed333f987b7a18e/llvm/lib/CodeG…
74 but here we use the terminology from clang-tidy).
91 ------------------------------
114 While switching coding standard will make it easier to use non-acronym names for
122 their non-acronym form e.g. ``Triple T`` → ``Triple triple``.
188 --------------------------------
198 -------------
216 * Some large-scale renaming may happen anyway, leading to its disadvantages
220 --------
228 It goes against a policy of avoiding large-scale reformatting of existing code
243 **Mitigation**: `git-hyper-blame
244 …https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-hyper-bl…
246 A ``.git-blame-ignore-revs`` file identifying the variable renaming commits
249 <https://public-inbox.org/git/20190324235020.49706-1-michael@platin.gs/>`_
255 There are many forks of LLVM with downstream changes. Merging a large-scale
258 **Mitigation**: A large-scale renaming would be automated. A fork maintainer can
281 #. Update the `policy page <../CodingStandards.html>`_. This will explain the
286 1. Add or change the project's .clang-tidy to reflect the agreed rules.
290 2. Apply ``clang-tidy`` to the project's files, with only the
291 ``readability-identifier-naming`` rules enabled. ``clang-tidy`` will also
292 reformat the affected lines according to the rules in ``.clang-format``.
293 It is anticipated that this will be a good dog-fooding opportunity for
294 clang-tidy, and bugs should be fixed in the process, likely including:
296 * `readability-identifier-naming incorrectly fixes lambda capture
298 * `readability-identifier-naming incorrectly fixes variables which
300 * `readability-identifier-naming misses fixing member variables in
311 Some items may not make sense to rename individually - it is expected that
316 * clang-tools-extra
329 * RISC-V backend
338 * compiler-rt
340 * openmp
341 * parallel-libs
352 …oding Conventions https://llvm.org/svn/llvm-project/lldb/branches/release_39/www/lldb-coding-conve…
353 .. [Google] Google C++ Style Guide https://google.github.io/styleguide/cppguide.html#Variable_Names
354 .. [WebKit] WebKit Code Style Guidelines https://webkit.org/code-style-guidelines/#names
356 .. [Rust] Rust naming conventions https://doc.rust-lang.org/1.0.0/style/style/naming/README.html
357 …wift API Design Guidelines https://swift.org/documentation/api-design-guidelines/#general-conventi…
358 …] Style Guide for Python Code https://www.python.org/dev/peps/pep-0008/#function-and-variable-names
359 …la Coding style: Prefixes https://firefox-source-docs.mozilla.org/tools/lint/coding-style/coding_s…
360 .. [SVE] LLVM with support for SVE https://github.com/ARM-software/LLVM-SVE
361 …[AminiInconsistent] Mehdi Amini, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130329.html
362 …[ArsenaultAgree] Matt Arsenault, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129934.html
363 …BeylsDistinguish] Kristof Beyls, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130292.html
364 …[BradburyConcern] Alex Bradbury, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130266.html
365 …adburyTransition] Alex Bradbury, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130388.html
366 …arruthAcronym] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130313.html
367 …ruthCamelBack] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130214.html
368 …thDistinguish] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130310.html
369 …rruthFunction] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130309.html
370 …hInconsistent] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130312.html
371 …[CarruthLower] Chandler Carruth, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130430.html
372 .. [DasInconsistent] Sanjoy Das, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130304.html
373 …[DenisovCamelBack] Alex Denisov, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130179.html
374 … [EmersonConcern] Amara Emerson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129894.html
375 …GreeneDistinguish] David Greene, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130425.html
376 .. [GreeneGitBlame] David Greene, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130228.html
377 …endersonPrefix] James Henderson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130465.html
378 …hnleDistinguish] Nicolai Hähnle, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129923.html
379 …icDistinguish] Nemanja Ivanovic, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130249.html
380 .. [JonesDistinguish] JD Jones, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129926.html
381 … [LattnerAcronym] Chris Lattner, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130353.html
382 .. [LattnerAgree] Chris Latter, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129907.html
383 …[LattnerFunction] Chris Lattner, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130630.html
384 .. [LattnerLower] Chris Lattner, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130629.html
385 …attnerTransition] Chris Lattner, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130355.html
386 …tinDistinguish] Danila Malyutin, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130320.html
387 …zekAcronym] Krzysztof Parzyszek, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130306.html
388 …ekAcronym2] Krzysztof Parzyszek, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130323.html
389 …istinguish] Krzysztof Parzyszek, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129941.html
390 .. [PicusAcronym] Diana Picus, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130318.html
391 .. [ReamesConcern] Philip Reames, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130181.html
392 .. [RicciAcronyms] Bruno Ricci, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130328.html
393 .. [RobinsonAgree] Paul Robinson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130111.html
394 …insonDistinguish] Paul Robinson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/129920.html
395 …nsonDistinguish2] Paul Robinson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130229.html
396 …binsonTransition] Paul Robinson, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130415.html
398 .. [TurnerLLDB] Zachary Turner, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130213.html
399 .. [Ueyama] Rui Ueyama, http://lists.llvm.org/pipermail/llvm-dev/2019-February/130435.html