Lincoln Atkinson

The printf feature has definitely not been broken for the past ~year or whenever it was debuted. So why does it now have an off-by-1 bug? Maybe there is a...

Perhaps more clear: ``` fsharp let chart = [1..10] |> List.map (fun n -> (n, n)) |> Chart.Line [chart |> Chart.WithTitle(Text = "ABC") chart |> Chart.WithTitle(Text = "XYZ")] |> Chart.Rows...

Bringing over some context from original issue at fsharp/fsharp: > @latkin said: > This looks like a parser bug. Maybe the parens are required, but if so you should get...

@bbenoist I typically use ILSpy, which seems to have the same problem. It's smart enough to show the attributes in the "C# View", yet doesn't show them in the "IL...

You can use standard convention of prefixing the identifier with _, which tells the compiler to ignore that identifier when computing 1182. ``` fsharp query { for _x in [1;2;3]...

@asik -- scenarios like this are exactly why the `NonStructuralComparison` operators were added in F# 4.0. ``` fsharp [] type MyVal = val X : int new(x) = { X...

Yes, simply opening `NonStructuralComparison` is a bit blunt. See [this convo](https://twitter.com/LincolnAtkinson/status/593592474838257664), and an approach for encapsulating `NonStructuralComparison` in dedicated operators [here](https://gist.github.com/latkin/361c59a7582e390167c7).

Yes, looks like some inconsistencies in generic comparison with `NaN`. FWIW this is not a 4.0 regression, it has been like this for a few releases. @manofstick does any of...