[
https://issues.apache.org/jira/browse/IGNITE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134088#comment-15134088
]
Pavel Tupitsyn edited comment on IGNITE-1563 at 2/5/16 12:42 PM:
-----------------------------------------------------------------
1) This is really a moot point. If user puts default(T) in .NET, he may expect
null in java, which is a default for all types.
"where corresponding structure has different default": ref types always default
to null, val types always default to all fields default, there is no way to
change this.
2) Fixed.
3) I don't think that we should, since they incur JNI call, and possibly a
network trip. See guidelines:
https://msdn.microsoft.com/library/ms229054(v=vs.100).aspx
4,5,6) Done.
was (Author: ptupitsyn):
1) This is really a moot point. If user puts default(T) in .NET, he may expect
null in java, which is a default for all types.
"where corresponding structure has different default": ref types always default
to null, val types always default to all fields default, there is no way to
change this.
2) Fixed
3) Not sure if we should, since they incur JNI call, and possibly a network
trip. See guidelines: https://msdn.microsoft.com/library/ms229054(v=vs.100).aspx
4)
> .Net: Implement "atomic" data structures.
> -----------------------------------------
>
> Key: IGNITE-1563
> URL: https://issues.apache.org/jira/browse/IGNITE-1563
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.5.0.final
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> This includes:
> atomicSequence;
> atomicStamped;
> atomicReference
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
