Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

194
Visualizações
Why isn't this class reference ambiguous?

I am wondering why this situation is not resulting in an ambiguous reference between types, one a class within our library and one an external struct. Consider the following-

External struct-

namespace External.Models
{
    public struct ProxyUser
    {
        public string Username { get; set; }
        public string Password { get; set; }
    }
}

Our class-

namespace MyApp.Configuration
{
    public class ProxyUser
    {
        public string Username { get; set; }
        public string Password { get; set; }
    }
}

Then the calling code approximates-

using External.Models;

namespace MyApp.Configuration.Factories
{
    sealed class Factory
    {
        public async Task<T> BuildConfiguration<T>()
        {
            var proxy = new ProxyUser { Username = username, Password = password }; // I would expect this to be ambiguous, but it references out class
        }
    }
}

This is a NetStandard 2.0 library if that makes a difference. Behavior is the same if I make our class a struct. Why isn't this ambiguous?

EDIT - Class is sealed, again if that makes a difference...

ANSWER

As @Sinatr mentioned, it appears to be related to this question- https://stackoverflow.com/a/25437586/14872099

This is a demonstration of the different behaviors I observed.

This resolves to our MyApp.Configuration.ProxyUser-

using External.Models;

namespace MyApp.Configuration.Factories
{
    sealed class Factory
    {
        public async Task<T> BuildConfiguration<T>()
        {
            var proxy = new ProxyUser { Username = username, Password = password }; // resolves to our class
        }
    }
}

This resolves to the external struct-

namespace MyApp.Configuration.Factories
{
    using External.Models;

    sealed class Factory
    {
        public async Task<T> BuildConfiguration<T>()
        {
            var proxy = new ProxyUser { Username = username, Password = password }; // resolves to external struct
        }
    }
}

Moving our class to another namespace creates ambiguity-

using External.Models;
using MyApp.Configuration.Models; // moved our class to this namespace

namespace MyApp.Configuration.Factories
{
    sealed class Factory
    {
        public async Task<T> BuildConfiguration<T>()
        {
            var proxy = new ProxyUser { Username = username, Password = password }; // this is ambiguous
        }
    }
}
over 4 years ago · Santiago Trujillo
1 Respostas
Responde à pergunta

0

Internal namespaces (i.e. inside the namespace brackets) get priority over external namespaces (i.e. using statements before the namespace block).

Note: "internal" and "external" aren't official definitions here, I just use these to easily distinguish between them.

Due to nesting, your namespace MyApp.Configuration.Factories block inherently also looks at any direct ancestors (MyApp.Configuration and MyApp), but not sibling namespaces (e.g. MyApp.Configuration.Services).

When a non-ambiguous reference is found in the internal namespaces, the system never bothers to check the external namespaces, and thus does not find a conflict. You'd only encounter a conflict if:

  • There are two valid options in the internal namespace, e.g. MyApp.Configuration.ProxyUser and MyApp.Configuration.Factories.ProxyUser
  • There are two valid options in the referenced external namespaces, e.g. External.Models.ProxyUser and Another.Namespace.ProxyUser (assuming both are referenced with using statements in this file)
over 4 years ago · Santiago Trujillo Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda