error-message | 📋 Error message component | Form library

Fwiw, I'm curious to know the same thing: if there's a way to avoid the $_ replacement or preserve or access the prior value in the exception context.

That said, I do know you can work around it by assigning $_ to a new variable as the first line of the loop:

It should be

You can simplify your code by having only a single validation routine. You can fix the error you mention, having only a single error at a time, by using the current state as passed into setState by the framework. The construct for this is

Somehow this seems to be related to using v-model on hidden fields.

Changing the code from:

You can't just add type annotations in function parameter destructuring like that. Change your code to this:

As of right now, you need to must know the roundId yourself. You could do this by observing the rounds as they are submitted on-chain and recording the roundId's (this could be recorded off-chain or on-chain, although on-chain may get expensive). This process may be made easier in the future.

The error message is due to the wrong feed address being pointed to in the constructor. Try this line instead:

TL;DR: The problem mainly comes from the constant loop bound and not directly from Eigen. Indeed, in the first case, Eigen store the size of the vectors in vector attributes while in the second case, you explicitly use the constant N.

Clever compilers can use this information to unroll loops more aggressively because they know that N is quite big. Unrolling a loop with a small N is a bad idea since the code will be bigger and has to read by the processor. If the code is not already loaded in the L1 cache, it must be loaded from the other caches, the RAM or even the storage device in the worst case. The added latency is often bigger than executing a sequential loop with a small unroll factor. This is why compilers do not always unroll loops (at least not with a big unroll factor).

Inlining also plays an important role in this code. Indeed, if the functions are inlined, the compiler can propagate constants and know the size of the vector enabling it to further optimize the code by unrolling the loop more aggressively. However, if the functions are not inlined, then there is no way the compiler can know the loop bounds. Clever compilers can still generate conditional algorithm to optimize both small loops and big ones but this makes the program bigger and introduces a small overhead. Compilers like ICC and Clang do generate the different code alternatives when the code can be vectorized but the loop bounds are unknown or also when aliasing is not known at compile time (the number of generated variants can quickly be huge and so the code size).

Note that inlining functions may not be enough since the constant propagation can be trapped by a complex conditionals dealing with runtime-defined variables or non-inlined function calls. Alternatively, the quality of the constant propagation may not be sufficient for the target example.

Finally, aliasing also play a critical role in the ability of compilers to generate SIMD instructions (and possibly better unroll the loop) in this code. Indeed, aliasing often prevent the use of SIMD instructions and it is not always easy for compilers to check aliasing and generate fast implementations accordingly.

If the vector-based implementation use a loop bound stored in the vector objects, then the code generated by MSVC is not vectorized in the benchmark: the constant is not propagated correctly despite the inlining of the function. The resulting code should be much slower. Here is the generated code:

vector I swap with is constant

It's not constant, but it's an anonymous temporary, so it can only bind to a const ref.

What is the new recommended way of releasing the memory of a vector if you can't swap it away?

Well, you can swap it away, if you want to stay backwards compatible and/or don't trust shrink_to_fit(). You just have to name your temporary:

Seems that you are unomunting you whole modal component when the user submits the form, killing the AnimatePresence in the process. try something like this: