Head to Head: Scott Allen and Jon Skeet
summary
Five Stack Overflow .NET puzzles get concrete answers: IQueryable accepts Func vs Expression<Func> so ORMs can translate queries to SQL while IEnumerable runs delegates locally causing unexpected data pulls; LINQ operators can be deferred vs greedy (ToList, OrderBy force materialization or full sorting) and yield return creates streaming behavior; Random is deterministic unless replaced by RNGCryptoServiceProvider for cryptographic randomness; tail-call elimination depends on the JIT/CLR (more likely in 64-bit release), so behavior varies by runtime.
AI-written summary · about
chapters (4)
- 0:00Start
- 9:52The Difference between Ienumerable and Iqueryable
- 27:54Why Is It Faster To Process a Sorted Array than an Unsorted Array
- 57:12It Should Be the Ccr Compiler Being Able To Look at that Function and Saying Ah I See the Last Thing You'Re Doing Is Making a Function Call to Yourself Again So Let Me Just Reuse the Same Stack Frame That I Just Created Hmm Thereby Not Continually Allocating Stack Frames Okay so Thinking of Stack from the Bottom this Time You Can Think either Way So Here We Have Full of 0 and in Full of 1 4 2 4 3 4 4 Etc Something It Can Be Optimized with Tail Calls if You Can Say Rightful of 0 Calls for 1 but I'M Bulb with this Stack I'Ll Just Put Full of 1 on the Same Thing 4 2 4 3 4 4 and Then So this Is a Method That Returns Void We Could Return I and either Way You Can Just Say Well You Know We Don't Need To Come Back We Can Just Return the Same Thing
