trade | trade Trade TRADE epitech | Cryptocurrency library

I had the same issue - regex library was updated from 2022.3.2 to 2022.3.15. You can set version in requirements for a while issue will fixed in next version.

The comment from @user207421 is spot on. If a language does not natively support double dispatch, no design pattern can alter the language to make it so. A pattern merely provides an alternative which may solve some of the problems that double dispatch would be applied to in another language.

People learning the Visitor Pattern who already have an understanding of double dispatch may be assisted by explanations such as, "Visitor solves a similar set of problems to those solved by double dispatch". Unfortunately, that explanation is often reduced to, "Visitor implements double dispatch" which is not true.

The fact you've recognized this means you have a solid understanding of both concepts already.

Don't do complicated things. To compute the cumulated positive differences, you just want to sum the diff ignoring the negative values (with clip).

Let's just do that:

It looks like your sticking point is figuring out how to access the values of the density curve at a given value of x or y.

You can use ggplot_build() to access the underlying data.frame constructed by the geom_density function. Here is some further discussion.

This should work

In your call of nx.draw you still have the fixed node size. I guess you want to have

If it's using RBP as a frame pointer at all, yes, mov %rbp, %rsp would be more compact and AFAIK at least as fast on all x86 microarchitectures. (mov-elimination probably even works on it). Even moreso when the add constant doesn't fit in an imm8.

This is probably a missed optimization, very similar to https://bugs.llvm.org/show_bug.cgi?id=10319 (which proposes using leave instead of mov/pop, which would cost 1 extra uop on Intel but save another 3 bytes). It points out the overall static code size savings are pretty small in normal cases, but isn't considering efficiency benefits. In normal builds (-O2 without -fno-omit-frame-pointer) only a few functions will use a frame pointer at all (only when using VLA / alloca, or over-aligning the stack) so the possible benefit is even smaller.

It seems from that bug that it's just a peephole the LLVM doesn't bother to look for, because many functions also need to restore other registers, so you actually need to add some other value to point RSP below other pushes.

(GCC sometimes uses mov to restore call-preserved regs so it can use leave. With a frame pointer, that makes the addressing mode fairly compact to encode, although a 4-byte qword mov -8(%rbp), %r12 is still not as small as 2-byte pop of course. And if we don't have a frame pointer (e.g. in -O2 code), mov %rbp, %rsp was never an option.)

Before considering the "not worth looking for" reason, I thought of another minor benefit:

After calling a function that saves/restores RBP, RBP is a load result. So after mov %rbp, %rsp, future use of RSP would need to wait for that load. Possibly some corner cases end up bottlenecked on store-fowrwarding latency, vs. register modification just being 1 cycle.

But that seems unlikely to be worth the extra code size in general; I expect such corner cases are rare. Although that new RSP value is needed for a pop %rbp, so then the caller's restored RBP value is the result of a chain of two loads after we return. (Fortunately ret has branch prediction to hide latency.)

So it might be worth trying both ways in some benchmarks; e.g. comparing this vs. a tweaked version of LLVM on some standard benchmarks like SPECint.

Just write historyApiFallback: true. It should work.

Never really worked with sf and friends before, but after reading the docs I could imagine a solution like this to fulfill your needs.

Since sf are in fact extended data.frames they naturally come with an rbind functionality. Having said that, the whole task should be as easy as rbind'ing all the relevant paths together. As for the waiting time, simply repeat the last row in the sf a couple of times, which would give you the impression of the vehicle stopping at B (and A on the way back).