Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/incubator-commonsrdf/pull/26#discussion_r85335505
--- Diff: api/src/main/java/org/apache/commons/rdf/api/Quad.java ---
@@ -17,16 +17,30 @@
*/
package org.apache.commons.rdf.api;
+import java.util.List;
+import java.util.Map;
import java.util.Objects;
import java.util.Optional;
+import java.util.Set;
/**
* A Quad is a statement in a
* <a href= "http://www.w3.org/TR/rdf11-concepts/#section-dataset"; >RDF-1.1
* Dataset</a>, as defined by
- * <a href= "https://www.w3.org/TR/2014/NOTE-rdf11-datasets-20140225/";
>RDF-1.1
+ * <a href=
"https://www.w3.org/TR/2014/NOTE-rdf11-datasets-20140225/#quad-semantics";
>RDF-1.1
* Concepts and Abstract Syntax</a>, a W3C Working Group Note published on
25
* February 2014.
+ * <p>
+ * A {@link Quad} object in Commons RDF is considered <em>immutable</em>,
that
+ * is, over it's life time it will have consistent behaviour for its
+ * {@link #equals(Object)} and {@link #hashCode()}, and the instances
returned
+ * from {@link #getGraphName()}, {@link #getSubject()}, {@link
#getPredicate()}
+ * and {@link #getObject()} will have consistent {@link
Object#equals(Object)}
+ * behaviour.
+ * <p>
+ * Thus, a {@link Quad} is thread-safe and can be safely used in
collections
--- End diff --
For thread-safety, must we not also either guarantee that any `setSubject`
etc. methods are atomic or that there are none (much the likelier story)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
