Manu Evans

I would have imagined that you didn't have to write or maintain `fastcc`; I would have imagined it's just hanging out in an enum somewhere in LLVM somewhere because it's...

Hmm, well, I'm going to use `fastcc` because the alternative is much more trouble, and you already seem to have done the work! I reckon it'd be a cool move...

Erm... ```c++ .Case("fastcall", llvm::CallingConv::X86_FastCall) ... .Case("fastcc", llvm::CallingConv::Fast) ... .Case("x86_fastcallcc", llvm::CallingConv::X86_FastCall) ``` ...so, was `fastcall` (which I tried originally) supposed to work? Maybe this map isn't quite right?

And, it actually looks like [X86_FastCall](https://llvm.org/doxygen/namespacellvm_1_1CallingConv.html#a040313cca4b689f07fb0fadc0f80b858afde87569738f9e23963e8735f71c33eb) is actually what I want here... even though `fastcc` does work, the spec is not as precise. Not clear why `fastcall` didn't actually work?...

I think the result of this work, would be for imports that are only used in some conditions (in versions, or in templates) to naturally migrate inside their respective conditional...

> > I think the result of this work, would be for imports that are only used in some conditions (in versions, or in templates) to naturally migrate inside their...

> You could potentially do a mock-up search of the identifiers present in the template constraint, provided that you somehow get a grip on the scope of the template constraint,...

The template seems irrelevant in this example, this situation can happen in any static-if series. It kinda looks like static if condition expressions are the same as function constraint expressions...

0.25 is extremely slow... how about every 0.01 seconds? Will scripting be able to deal with that frequency? I think the essence of what I'm suggesting is because these are...

> There is no need to poll every 50ms if, for example, TuyaMCU sends update every 5 seconds. I'm sorry; of course, this is naturally true, and it's subject to...