somestuff | repository contains my various stuffs | Frontend Framework library

You can add it as a method in the script tag

As explained in the doc, you need to include your path specific rules in a match /databases/{database}/documents block like:

Storing a pointer to ComplexClass would work, but using a raw pointer would be unwise. Use std::shared_ptr.

Alternatively, you could delete the copy constructor & assignment, and then store Bla in shared_ptrs when you do need assignments.

And instead of deleteing the copy operations, you can:

• Make them private, and add a member function with a long scary name that performs them, in case you need them.
• Delete just the copy assignment, and make the copy constructor explicit. Then a = b; wouldn't compile, but a = Bla(b); still would.

Having multiple threads simultaneously use the same TCP socket is possible in that most operating systems support it (i.e. you won't crash), but it's not useful because it's unpredictable which thread will end up receiving which bytes of data from the socket (or conversely, which thread will end up sending which bytes of data to the socket when) -- in either case your TCP data will end up getting randomly send to your various threads, which is a big problem if your messages are ever longer than one byte long.

What you can do, OTOH, is have one thread that is dedicated to only reading from the TCP socket, and when it has read in a full message, it hands that message over to one of the other threads (using a mutex-protected FIFO queue and a condition-variable, or similar) for processing. If the processing-thread later wants to send data back to the TCP socket, it would hand the data back to the network-thread via another FIFO queue, and then the network thread would take care of pulling the data out of the FIFO and writing it out to the TCP socket. In that design, because only one thread has access to the TCP socket, you can guarantee that messages boundaries are respected and messages do not get mixed up with each other.

Note that in order to have the network thread handle both reading and writing (and responding to incoming messages on its FIFO queue) in a timely manner, you may want to have it use non-blocking I/O and event-loop that blocks only inside select().

Promises' then accept a function. So, it should be:

The real problem is that your real project is always rebuild due to the metadata Outputs.

The special point is that you should make sure the validity and legitimacy of the value of Outputs.

The problem is under %(RelativeDir) of %(RelativeDir)%(Outputs). When you add it, the outputs has an illegal folder structure rather than a file which makes the outputs always find the missing illegal folder structure so that causes the project always rebuild.

Let me describe it in detail,

when msbuild reads outputs proeperty, when it reads till %(RelativeDir)%(Filename).cpp;%(RelativeDir)%(Filename).h;%(RelativeDir), the value of Outputs is this:

You can use a loop to simulate tree-walking:

As an alternative Maybe you can achieve it with Object.

Try:

r"https?:[^\s]+"