I'm seeing another strange behavior that seems independent from other stuff I've found today. It seems that the mere presence of a breakpoint on a line can affect the computation.
I'm using Linqpad 6.5.5 x64
.NET Core version (host): 3.0.0
.NET Core version (queries): 3.0.0
Roslyn Version: 3.3.1-beta4-19462-11
FSharp.Compiler.Service version: 220.127.116.11
Here's the reproduction.
- Create a C# statements script
Console.WriteLine(Math.Sqrt(1)); Console.WriteLine(Math.Sqrt(1)); // breakpoint Console.WriteLine(Math.Sqrt(1)); Console.WriteLine(Math.Sqrt(4)); Console.WriteLine(Math.Sqrt(4)); // breakpoint Console.WriteLine(Math.Sqrt(4)); Console.WriteLine(Math.Sqrt(9)); Console.WriteLine(Math.Sqrt(9)); // breakpoint Console.WriteLine(Math.Sqrt(9));
- Set breakpoints on the appropriate lines.
- Ensure compiler optimizations are turned off.
- Execute the script.
- For each breakpoint, just continue the script.
The final output (on my machine) is
1 1.0000000000000278 1 2 2.0000000000000555 2 3 3.000000000000074 3
let me introduce my new CSV data context dynamic driver.
- create new data context from CSV files, one table per file
- automatic relations detection
More info and download here:
Any comments and suggestions are welcome.
Happy CSV querying
Is it going to be possible to use Linq-pad with .net 5.0 (vNext), and if so what steps need to be taken?
This is part question (is this possible and how) and partly to make people aware of an upcoming issue as .net 5.0 moves to release version
Just had a strange one, not sure how to reproduce but basically I ran a 'SQL' query in one tab, changed back to a 'C# Expression' in another tab to run it and the Language dropdown had changed from the usual options to showing actual language options e.g. English (United States).
Not a big deal, just closed it and reopened it and all was good.