Skip to content

Possible compiler bug, I need your advice. #5512

@sebas77

Description

@sebas77

Hi,

The only way to report this issue is to upload the project, as the structure of the project, and not just the code, affects the outcome. However, I would like to show you what leads me to think it's a compiler bug before to proceed further.

image
image

If my assumptions about how the compiler works are right, this looks to me like a paradox. QuickSaveEngine.cs cannot be compiled if LocalInputEntityStruct is not compiled first and LocalInputEntityStruct cannot be compiled if it's nullable, right? The struct itself is 100% unmanaged and doesn't have nullable fields, but since it's a complex struct, the implementation of the interface with unmanaged constraint is my way to prove it. If you agree that there is something fishy, please let me know if and how I should proceed. Note: the same code compiles if I don't use separate assemblies.

OS info:

Windows 10, MSBuild 2017 (c# 7.3)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions