[
https://issues.apache.org/jira/browse/IGNITE-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944725#comment-15944725
]
Pavel Tupitsyn commented on IGNITE-3510:
----------------------------------------
Common way to organize types is to put public and internal in the same
namespace, without having a separate namespace for internal stuff. However,
this would be too big of a change for us and without any real benefit.
> .NET: Review namespace structure
> --------------------------------
>
> Key: IGNITE-3510
> URL: https://issues.apache.org/jira/browse/IGNITE-3510
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .net, breaking-api
> Fix For: 2.0
>
>
> Current issues:
> * Impl namespace contains both public and internal types.
> * Some classes (QueryBase, AffinityFunctionBase, etc) are not intended to be
> used directly, but they have to be public
> Need to review framework design guidelines and see how well-known APIs (.NET,
> WPF, Entity Framework) handle such issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
