However do not set that option permanently (and also disable RemoveSemicolon by
default), since the clang-format manual states that these options can lead to
incorrect formatting and thus their result should be carefully reviewed.

The regression was introduced in commit
84d792bc, when leads/lags were allowed on
model-local variables. The treatment of model-local variables without
leads/lags was negatively impacted. This commit fixes the regression by
restoring the former behaviour for model-local variables without leads/lags.

Reported on https://forum.dynare.org/t/pre-processing-takes-very-long/26865

Ref. dynare#1929

– New “heterogeneity_dimension” statement
– New option “heterogeneity” to “var”, “varexo”, “parameters”, “model” and
  “shocks” statements
– New “SUM()” operator in “model” block

Rather use the data member which already exists.

Ref. dynare#1929

Automatically detected by clang-tidy with performance-move-const-arg check.

Do not make the modification for Tokenizer::location type, since we have no
guarantee that the type will remain trivially-copyable in the future.

Also add some annotations to remove some false positives.

There remain some boost-related false positives, it’s unclear how to suppress
them.

Automatically detected using clang-tidy with bugprone-reserved-identifier
check.

By the way, homogeneize the define identifiers in relation to camel case
convention.

Automatically detected using clang-tidy with modernize-use-nodiscard check.

Initialization with initalizer list is nicer. And, more importantly,
initialization with parentheses is not supported by Clang < 16.

This allows the compiler to better optimize by inlining those call when worth
it.

The C99 copysign() function was used in the generated C output, but that
function does not correctly handle zero. Replace it by a custom sign()
function.

Use map::{try,}emplace() instead of operator[], which should in theory be
slightly faster.

The function is now provided separately by Dynare.jl.

The new representation is only supported for MATLAB/Octave, C and Julia output
for the time being. Bytecode and JSON are unsupported.

This commit adds new fields in M_.

This is a preliminary step for dynare#1859.

– DataTree::packageDir() now takes a std::string_view, returns a
  std::filesystem::path, and no longer creates that directory
– DataTree::writeToFileIfModified() now takes a std::filesystem::path as
  argument
– Do not call DataTree::writeToFileIfModified() for generating MATLAB/Octave
  files, since it does not work (the directory inside which the file is written
  has been deleted by the preprocessor just before)
– Consistently use DataTree::packageDir() everywhere (for compatibility with
  planner_objective)

By the way:
– improve the semantics by having a consistent treatment of empty substring
  components (previously, only the last one was ignored)
– move it to DataTree to make it more accessible from elsewhere (even though
  ideally it should be in a “utilities” namespace).

By the way, turn those classes into structs since all their members are public.

– factorize common code between the static and the dynamic version
– reorganise language-specific code into dedicated functions
– use a function template in the main helper to do some computations
  at compile-time (using constexpr features)

We follow the advice given by Josuttis in his book about move semantics.

Deleting those member fuctions can be a bug if we want to allow copy semantics,
because overload resolution will no longer fallback to the copy
constructor/assignment operator when given an rvalue.

In particular, this explain why it was not possible to delete the move
assignment operator of the StaticModel class.

Ref. dynare#1852

Otherwise clang emits this warning:
 using directive refers to implicitly-defined namespace 'std'

Ref. Madysson/estimation-codes#5

Closes: #85

This option tells the preprocessor not to use the commutativity of addition and
multiplication when looking for common subexpressions.

As a consequence, when using this option, equations in various outputs (LaTeX,
JSON…) will appear as the user entered them.

There is however a potential performance cost to using this option, yet to be
determined.

Ref. dynare#1788

Ref. DynareJulia/Dynare.jl#1

Also, do various other cosmetic/simplification changes.

This permits some simplifications.

stop processing when certain functions are used in a linear context on endogenous/exogenous variables. closes dynare#1537