From array documentation: The array size is limited to a total of 4 billion elements, and to a maximum index of 0X7FEFFFFF in any given dimension (0X7FFFFFC7 for byte arrays and arrays of single-byte structures).
It's much easier to abuse the type system with the System.Runtime.CompilerServices.Unsafe.As method :D. But the tricks used in the presentation are cool too.
That API was added starting in .NET Core (sometimes even versions like 3.1). I was working on these tricks way before than and they work in .NET Framework as well.
My god this is the best C# talk I've seen
Maybe the first presentation I have found where a mere 1.25x speed makes the speaking too fast. I like it!
I was suprised by the second presentation. Some editing mistake?
The accent makes me think he's a super-villain.
The presentation makes me certain of it.
13:22 console applications, too!
Awesome 2 hours thanks!
Brilliant
When a system developer is forced to write in C# for some time and decide to bend to language for his needs and not be bended by this language :)
No sound?
Yep
Does the source code happen to be somewhere?
All the code is scattered around on the blog. blog.adamfurmanek.pl/2016/05/21/virtual-and-non-virtual-calls-in-c/
wait. wouldn't that mean arrays are limited to 2^31-1 elements?
that can't be right, can it?
From array documentation: The array size is limited to a total of 4 billion elements, and to a maximum index of 0X7FEFFFFF in any given dimension (0X7FFFFFC7 for byte arrays and arrays of single-byte structures).
@@ladislavseps4801 that's... horrible
isn't java only 2 billion? Do you really need an array with more than 4 billion elements? that's 4 billion 32 bit addresses lol
2x1 videos
No sound :/
It's much easier to abuse the type system with the System.Runtime.CompilerServices.Unsafe.As method :D. But the tricks used in the presentation are cool too.
That API was added starting in .NET Core (sometimes even versions like 3.1). I was working on these tricks way before than and they work in .NET Framework as well.