Is UserManager.IsEmailConfirmedAsync only needed when you don't already have an IdentityUser object?

[winzig]

I've come across a lot of code that looks like this sample from the repo:

aspnetcore/src/Security/samples/Identity.ExternalClaims/Pages/Account/ForgotPassword.cshtml.cs

Lines 38 to 39 in 53682c0

	var user = await _userManager.FindByEmailAsync(Input.Email);
	if (user == null || !(await _userManager.IsEmailConfirmedAsync(user)))

Am I crazy, or could that second line simply use user.EmailConfirmed instead of calling IsEmailConfirmedAsync():

aspnetcore/src/Identity/Extensions.Stores/src/IdentityUser.cs

Line 91 in 728110e

public virtual bool EmailConfirmed { get; set; }

I've spelunked through the code and I think so, but it's a bit hard to follow, but it seems as though IsEmailConfirmedAsync ...

aspnetcore/src/Identity/Extensions.Core/src/UserManager.cs

Lines 1513 to 1522 in ce16ff0

	public virtual async Task<bool> IsEmailConfirmedAsync(TUser user)
	{
	ThrowIfDisposed();
	var store = GetEmailStore();
	if (user == null)
	{
	throw new ArgumentNullException(nameof(user));
	}
	return await store.GetEmailConfirmedAsync(user, CancellationToken);
	}

... just ends up returning the value of EmailConfirmed:

aspnetcore/src/Identity/Extensions.Stores/src/UserStoreBase.cs

Lines 472 to 481 in bfec2c1

	public virtual Task<bool> GetEmailConfirmedAsync(TUser user, CancellationToken cancellationToken = default(CancellationToken))
	{
	cancellationToken.ThrowIfCancellationRequested();
	ThrowIfDisposed();
	if (user == null)
	{
	throw new ArgumentNullException(nameof(user));
	}
	return Task.FromResult(user.EmailConfirmed);
	}

So is there some reason we can't just check user.EmailConfirmed?