There is a step Adding Export Configuration (Step 11) in CMake Tutorial.

There seems no related examples about Export Configuration In the repository, could you add one?

Hello, users of sol2! This issue was made so that I could get a better idea of what you all use for Lua and how much you like / dislike sol2 compared to what you used to use (if anything) and sol2 now. If anyone could just reply to this issue with their thoughts, perhaps answer some of the questions below (or go on a tangent, really anything), I'd appreciate it. I'm going to be writing a paper abo

PR #342 revamps the checking of bounds declarations. It contains some examples of checking. @lenary noted that none of the examples have unsequenced assignments, where the order in which assignments happen is not specified. This means that pending sets are always empty in the examples. We should add an example where there are some unsequenced assignments.

As the title says, Enumeration has two properties for the same information.

        public Type Type { get; set; }
        public BuiltinType BuiltinType { get; set; }

We should remove BuiltinType and have it just as a desugared property of Type.

from https://github.com/root-project/cling/blob/master/tools/Jupyter/README.md :

export PATH=/cling-install-prefix/bin:$PATH
cd /cling-install-prefix/share/cling/Jupyter/kernel

maybe should be replaced with

export PATH=$PATH:/cling-install-prefix/bin
cd /cling-install-prefix/share/cling/Jupyter/kernel

because cling is required but not clang.
The clang binary mus

Like shown here it would be great to have the possibility, to tell Bear suppressing unsupported compiler flags in the compile_commands.json.

Please write a small note in the documentation on -

1. How to associate Yavide with a folder of existing source code?
2. How to make source code navigation working with the folder mentioned above?

Say, for instance, I have cloned Linux kernel source code and I want to start making changes to the source using Yavide.

Thanks & regards,
Sreenath

As for Display the special operations generated by the compiler #224 discussion, the documentation will improve if we had a section describing the transformation of each featre and his limitations.

In particular for the special operation, to explain that only the operations that are really generated would appear in the transformation. This is due to the fact that the tool s based on the AST.

bug in README.md when_all_ready() example:

task<> example2()
{
...
// Unpack and handle each result individually once they're all complete.
for (int i = 0; i < 1000; ++i)
{
try
{
>>> std::string& record = tasks[i].result();
should be
std::string& record = resultTasks[i].result();
...
}

• incremental CTU (on the fly CTU with skip files) feature usage configuration, limitations when ready
• web UI usage
  • how to compare the previous (marked by tag, use the date filter) results of two runs (same run?)
• more simple and advanced use case examples
  • CI job for a quality review (check for high severity results and fail the job if any)
  • usage of the upcoming f

If you grab the header here:

It will scale down to the center of the monitor, and the cursor stays where you grabbed it, but AvalonStudio won't be at the cursor:

Expected

Description

Hi, ccache chooses the compiler to launch according to the following priority:

      # 1. Compiler specified on the command line with an absolute path
      # 2. Compiler specified with the CCACHE_CC env var
      # 3. Compiler specified on the command line with a relative path

But I need ccache to force a d

Hi, first of all I want to thank the author of this plugin, it is really good. And secondly, are there any plans on docbuffer?

Would be nice to see padding, in class members.

For field1 padding is:
offset of field2 - offset field1 - sizeof field1
or
size of class - offset of field1- size of field1

Priority: Low

@OvermindDL1 says "I think all the tests should be adjusted to take the integer on the program parameters or an environment variable or something. That would both prevent such optimizations and would allow for easily CI'd consistency checks."

was just watching the C++ Now presentation on Julia and C++ (https://www.youtube.com/watch?v=hvnxY3NjHQ4) and noticed in the section on Cxx.jl (around 48 minutes in) that there is a special assignment syntax in the REPL ":=" for assigning C++ results back to a Julia variable.

I don't see this documented anywhere here in the docs.

When accessing members of an object (through a pointer), it's much faster and more convenient to simply write the . operator and have it automatically converted into a ->
Several IDEs offer this like QtCreator and VisualStudio.
eg:

Foo* Bar;
Bar.
// Magic :D
Bar->ContinueWritingHere

Thanks in advance