Lines Matching +full:docs +full:- +full:llvm +full:- +full:html

5 ---------------
7 Please refer to the `LLVM Getting Started Guide
8 <https://llvm.org/docs/GettingStarted.html>`_ for general information on how to
9 get started on the LLVM project. A detailed explanation on how to build and
10 test LLDB can be found in the `build instructions <build.html>`_ and `test
11 instructions <test.html>`_ respectively.
14 --------------------
16 Please refer to the `LLVM Developer Policy
17 <https://llvm.org/docs/DeveloperPolicy.html>`_ for information about
18 authoring and uploading a patch. LLDB differs from the LLVM Developer
21 For anything not explicitly listed here, assume that LLDB follows the LLVM
27 LLDB's code style differs from `LLVM's coding style <https://llvm.org/docs/CodingStandards.html>`_
30 …iable and function naming <https://llvm.org/docs/CodingStandards.html#name-types-functions-variabl…
39 * `Use of asserts <https://llvm.org/docs/CodingStandards.html#assert-liberally>`_:
43 `golden rule <https://llvm.org/docs/CodingStandards.html#introduction>`_
46 All new code in LLDB should be formatted with clang-format. Existing code may
53 Like LLVM it is important to submit tests with your patches, but note that  a
55 `test documentation <test.html>`_ for more details and the
56 `lldb/test <https://github.com/llvm/llvm-project/tree/main/lldb/test>`_ folder
62 --------------------------------------------
64 Contrary to Clang, which is typically a short-lived process, LLDB
72   error handling types such as `llvm::Expected<T>
73   <https://llvm.org/doxygen/classllvm_1_1Expected.html>`_ or
83   is convinced will always hold, regardless what an end-user does with
98   LLVM's crash handler, and then return execution. Use these sparingly
107   ``llvm::report_fatal_error()`` or ``abort()`` should be avoided at all
114 end-user.