[
https://issues.apache.org/jira/browse/IGNITE-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075415#comment-15075415
]
Dmitriy Setrakyan commented on IGNITE-2263:
-------------------------------------------
For as long as we have such view methods, we will keep running into
inefficiencies in code, simply because it is impossible to protect against
them. If a method receives a set or a list, how can you tell whether this is a
real list or a view over that list?
I would vote for completely getting rid of these methods and figuring out
another efficient way to support view-like behavior. For example, what if we
add multiple visit(...) methods allowing users to visit and filter the
collections explicitly, instead of trying to hide it from them.
> Get rid of wrapping views where possible.
> -----------------------------------------
>
> Key: IGNITE-2263
> URL: https://issues.apache.org/jira/browse/IGNITE-2263
> Project: Ignite
> Issue Type: Sub-task
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Critical
> Fix For: 1.6
>
>
> We have about ~50-100 usages of things like F.view or F.viewReadOnly. In lots
> cases it is not necessary, adds garbage, but doesn't add any value.
> Need to revisit these places.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
