It was something I hope you knew off the top of your head without spending time doing research. If it takes more than that, never mind and TY anyway. In the disassembler, I found the function addresses called located in the method table. Going to try to get it by slot and see if that works.

Yes, I have tried value and reference type arguments. Ive gone through the code and issues in your amazing SharpLab repo looking for anything about you handle generics. I was trying to what you do to show generic method addresses in disassembled JIT. Looks like PrepareMethod for the attribute types

something is strange w/how the the Runtime operates with generics. Ive flushed the instruction cache, played around w/different environmental variables for JIT and PGO, nothing works. in Windbg, it says System.Tuple.Create(!!0) is not jitted even though I invoked it and used PrepareMethod

let me give you another example. if I redirect the Enumerable.Where extension method, calling the extension method directly doesn't redirect. But if I call it as an extension method from an object of IEnumerable, it does redirect

Thank you so much for replying. I've read a lot of things you wrote on Github and you are highly intelligent and knowledgeable. I am trying to redirect a generic method in the BCL. Take a look at this in my repo to see what I am doing github.com/toupswork/Mo...

Basically, if I try to redirect something like Tuple<T>.Create, It doesn't work. none of the generic methods in the base class library are redirectable. I don't think it's Jitting

Pink Floyd was wrong: There is no dark side of the moon

Super cool!

Was on a call with Glenn Condron last week and he alluded to a change coming with async await. I asked if it was green threads, but no. He tried to explain, but he was short on time. I'm wondering if this is what he was talking about.

Interesting, the most sophisticated and knowledgeable AI ever creative would not vote for Trump

You all know who that presenter is? He created a library that he used to write a kernel mode driver in C# !! Yes, no freaking way. But that's not all: He wrote a C# game that loads during the boot process w/out an OS, by p/invoking UEFI libraries

David, the thing that totally blows my mind is the improved escape analysis, allowing reference types to be allocated on the stack. But thats not all: reference types with few fields can be stored in registers! So no reference type header, and the perf hit from Linq closures can sometimes be negated

Regular switch expressions are faster than a series of if...else statements because it does neat trick analogous to a hash set, where the value can be used to skip over case statements. For switch expressions, look at the lowered code it creates. You'll see it's really optimized

all the freaking time. can't live without it

To be fair, originally short-lived and long-lived were pronounced as in live tv. But at this point enough people pronounce it as in living, that dictionaries, but not all, say it that new way.
Same with gon-duh-luh: It used to be gon-DOH-la.

Realtor—For God's sake, it's Real-Tor, say it with me now
Moscow—there is no cow in Moss-Coh
Zoology—theres no Zoo in Zoe-Ology
Bestiality—theres no beast in BEST-Y-ality
Shortlived—Its live as in live television plus a D
Prelude—its prell-yude
Gondola—Gon-dOh-luh