Who wants to create a plugins for Unreal with me for fun/market

what do you mean? Are you advertising a job?

I wonder how to make it so that "co_await" wait for the arrival of data without parallelism and at the same time perform the main task

You can't do that. The function which calls co_await is suspended and hence it can't do anything else. In the calling function (the function which called the coroutine) where co_await returns, you can proceed with doing something else as long as you are not awaiting the result of the function which was suspended earlier Your example however is an use case for parallelism (using threads or tasks with promise and futures would be a better option).

Coroutines function are stored in the heap right?

Coroutines function are stored in the heap right?

I don't think so

The information needed to resume a coroutine is indeed stored in the heap (or free store). All the existing coroutine implementations (gcc, Clang, MS C++ ) in C++ are stackless. You have external libraries like CO2 which support stackful coroutines.

Yeah till C++ standard supports stackful coroutines

How do I access classes with C++ GetProcAddress? When I try to reach it, it returns a NULL value, the code I used to reach GetProcAddress(dllModule,"classname::Function")

But the programmer doesn't need to worry about memory leak, right? And how to distinguish between the function returning with co_yield or co_return? To avoid recalling it again

The standardisation process is slow, there is a talk in cpp podcast about whether the language is Dying or not

I don't know about that but I have moved on to C# and Rust

I like its macro system Sometimes I feel that trait bounding is too much restrictive

Anyway I feel this code should compile, but seems this feature is likely will be added later in the standard: consteval int foo(std::size_t size){ std::array<int, size> ar; return 0; }

It is being debated And there are reasons why this doesn't work. There is a difference between evaluation at compile time and instantiation at compile time. The arguments to a consteval function IMHO should not be treated as template arguments.

Compile time function doesn't exist in anyway, they are just resulted compile time computed values

I know what consteval is consteval int func(int& x){return -1;} int x{}; static_assert(func(x)==-1); Arguments to consteval functions need not be constant expression. Read this link to understand the arguments against consteval functions being used as template parameter arguments - https://stackoverflow.com/questions/56130792/will-consteval-functions-allow-template-parameters-dependent-on-function-argumen Read all the answers in that link Also think of a case like this which is not currently supported consteval auto func(int n){ if constexpr(n==0) return 1; else { using T = decltype(fn(n-1))*; return T{}; } } This doesn't work because consteval functions don't support instantiations at compile time which was always the idea behind them. They were meant to be evaluated at compile time rather than supporting instantiations of the sort you see with template functions. Supporting instantiations in consteval functions would defeat the type system consteval functions by their definition in the standard are parsed once and evaluated each time at the call site during compile time. This is very different from how template instantiations work. So like I said there is a difference between compile time evaluation and compile time instantiation (TMP included).

Did you know that network has been added to C++?

Which probably won't be supported since it goes against One definition rule

I guess it will be asio

Why? Consteval functions are not functions as you said. Why should this violate ODR? They just translate to compile time values. You seem to be contradicting yourself. And this was exactly my point on why consteval functions can't be treated as equivalent to template functions

You can't do that. The function which calls co_await is suspended and hence it can't do anything else. In the calling function (the function which called the coroutine) where co_await returns, you can proceed with doing something else as long as you are not awaiting the result of the function which was suspended earlier Your example however is an use case for parallelism (using threads or tasks with promise and futures would be a better option).

I'm still trying to process that, the possible edge cases I think my argument still valid; they are still compile time computed values, even if it requires instantiation of other templates entities This can just be treated or implemented equivalent to explicitly instantiate those entities everytime there is a call Since they are just computed values, then there should not be any definition at all to violate

😂

What is the best? Bring data from Data base to list and then deal with it Or it is better to deal with the data and it is surrounded there, but we call it at the time of the need

When I use the glm::toMat4(glm::quat(vec)) code in C++ OpenGL, the angle turns out to be incorrect, when I do 4.0 degrees, it becomes 45.0 degrees, what is the reason for this?

are you sure you are putting the right type of angle in there? radians vs degrees?

Hello, someone have a simple github repo for a methods post and get in C?

How can i install lib graphics.h on visual studio on c++ ?

How can i install lib graphics.h on visual studio on c++ ?

If it's a header only library you can grab the file directly to your project and start using it

How can i install lib graphics.h on visual studio on c++ ?

My guess it's that schools there just still follow the old materials and such

How can i install lib graphics.h on visual studio on c++ ?

Without curl or soup

How can i install lib graphics.h on visual studio on c++ ?

socketServer.c: In function ‘void receiveAndPrintIncomingDataOnSeparateThread(AcceptedSocket*)’: socketServer.c:38:28: error: invalid conversion from ‘void (*)(int)’ to ‘void* (*)(void*)’ [-fpermissive] 38 | pthread_create(&id, NULL,receiveAndPrintIncomingRequest,clientSocket->acceptedSocketFD); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | void (*)(int) In file included from socketServer.c:3: /usr/include/pthread.h:204:36: note: initializing argument 3 of ‘int pthread_create(pthread_t*, const pthread_attr_t*, void* (*)(void*), void*)’ 204 | void *(*__start_routine) (void *), | ~~~~~~^~~~~~~~~~~~~~~~~~~~~ socketServer.c:38:73: error: invalid conversion from ‘int’ to ‘void*’ [-fpermissive] 38 | eate(&id, NULL,receiveAndPrintIncomingRequest,clientSocket->acceptedSocketFD); | ~~~~~~~~~~^~~~~~~~~~~~~~ | | | int

What is pastebin?