Inline functions in a referenced project optimized incorrectly

[rca22]

In the attached example, we create three types;

• ID, in ClassLibrary1
• ID2, in ClassLibrary1, which relies on ID
• ID3 in ConsoleApp1, which relies on ID2.

In each of these we override equality and comparison operators, using inline functions to improve performance for ID3. (Note that this repro is a minimal example from more complicated code where this makes more sense!)

We create instances of each in the console app. and check that two unequal values of each type are reported as unequal by the compiler.
In Release mode only, the third assertion, that two obviously different instances of ID3 are unequal fails.

To repro, please run the attached program.
repro.zip

Expected behavior

I expect the program to exit with code 0.

Actual behavior

An exception is thrown in the last equality check, for aBarBar versus bBarBar

Known workarounds

Running this in debug mode fixes the issue.
Putting the definitions of ID and ID2 in the same project as ID3 fixes the issue. Because of this, I suspect this issue is something to do with incorrect optimisations around inlining functions from other projects.
Changing ID from a struct into a class by removing all the attributes associated with it fixes the issue.

Related information

Tested in .NET 8, SDKs 8.0.100 and 8.0.403
Windows 10.
VS 2022 for editing.

[vzarytovskii]

An exception is thrown in the last equality check, for aBarBar versus bBarBar

What's the exception? What's yielded in the nightly 9.0 sdk? Does it change with realsig off? It could also be related to the additional equality generated.

[rca22]

An exception is thrown in the last equality check, for aBarBar versus bBarBar

What's the exception? What's yielded in the nightly 9.0 sdk? Does it change with realsig off? It could also be related to the additional equality generated.

To be clear the last equality check reads if aBarBar = bBarBar then failwith "Expect aBarBar and bBarBar to differ"; earlier aBarBar and bBarBar are set up to be clearly different. The exception is not an internal one; just there to indicate the deviation from expected behaviour.

[vzarytovskii]

An exception is thrown in the last equality check, for aBarBar versus bBarBar

What's the exception? What's yielded in the nightly 9.0 sdk? Does it change with realsig off? It could also be related to the additional equality generated.

To be clear the last equality check reads if aBarBar = bBarBar then failwith "Expect aBarBar and bBarBar to differ"; earlier aBarBar and bBarBar are set up to be clearly different. The exception is not an internal one; just there to indicate the deviation from expected behaviour.

I see, thanks. It appears that it's failing in SDK 6.0, could've been there forever.

[T-Gro]

This is what the decompiled Release code looks like for the Equals check of ID3.
As you can see, the name ID4 was being reused for both sides, ending up comparing a string with the same string, all the time.

[vzarytovskii]

This is what the decompiled Release code looks like for the Equals check of ID3.
As you can see, the name ID4 was being reused for both sides, ending up comparing a string with the same string, all the time.

That's some awkward codegen. We will need to see whether it's a recent regression. If it is, we need to fix it for 9.0.200

[vzarytovskii]

Update, the new minimal repro:

Library.fs (this file should be in a separate project):

namespace Library

#nowarn "346"

[<Struct>]
type ID (value : string) =
    member _.Value = value
    member inline this.Hello(other: ID) = System.Console.WriteLine(this.Value + " " + other.Value)

type ID2 = { Value : ID } with
    member inline this.Hello(other: ID2) = this.Value.Hello other.Value

Program.fs:

open Library

[<EntryPoint>]
let main _ =

    let aBar = { Value = ID "a" }
    let bBar = { Value = ID "b" }

    aBar.Hello(bBar)

    0

It is also not the case with static members. So the issue is that local seems not to be introduced for the this parameter of the struct member.

Something must be missing in the optimization data/environment, since this doesn't happen if any of the following are met:

1. Library and program are in one project
2. ID type is a non-struct
3. ID2 type is a non-record