Two different ways of writing the query conditions, the translation statements are inconsistent

Two different ways of writing the query conditions, the translation statements are inconsistent

Steps to reproduce

var a = dbContext.Test.Where(a => !a.IsDeleted).FirstOrDefault();

SELECT TOP(1) [b].[IsDeleted]
FROM [Test] AS [b]
WHERE ([b].[IsDeleted] <> CAST(1 AS bit))

var b = dbContext.Test.Where(a => a.IsDeleted == false).FirstOrDefault();

SELECT TOP(1) [b].[IsDeleted]
FROM [Test] AS [b]
WHERE ([b].[IsDeleted] = CAST(0 AS bit))

Expected behavior

The translation statement is consistent and uses the second

Further technical details

EF Core version:3.0.0 Database provider: Microsoft.EntityFrameworkCore.SqlServer Target framework: NET Core 3.0 Operating system:Win10 IDE: Visual Studio 2019 16.3

[REscobar]

If IsDeleted is nullable, the expected behaviour is those two different queries

[ajcvickers]

We discussed this in triage and the general feeling is that, other than for correctness, we should translate what was written as closely as possible, especially where doing otherwise will perform differently on different back ends. However, we could revisit this if we find many people falling into a performance trap because of this.