Instructions

A specification is a formal statement about program behavior. A temporal property is a kind of specification that constrains the sequence of events that can or cannot occur on a single instance during an execution of a program. In this HIT, events are function calls in the Java programming language. You will first consider the documentation for a Java library and then use this documentation to check the validity of a temporal property related to the library. Each HIT contains 6 properties for you to verify.
An example of a true temporal property: close() is always preceded by open(). This property is true because in order to close a file, the file must first be open If this property does not hold (i.e., a program calls close() without first calling open() on the same object), an error occurs.
An example of a false temporal property: open() is always followed by close(). This property is false because an error does not necessarily occur if close() is not called after open(), even though it is good programming practice to do so. Note that a property is true ONLY IF a violation of the property results in an error (e.g., an Exception in Java) or the violation will never happen in the program.
You can participate our survey only if you pass the qualification test.

Question	Machine's Answer	Do you agree with machine's answer	Explain (At least 10 words)	How confident are you
1. In HashSet library, clear() is always followed by clone()	False	Agree Disagree *	*	*
2. In HashSet library, clear() is always immediately followed by clone()	False	Agree Disagree *	*	*
3. In HashSet library, clear() is never followed by clone()	False	Agree Disagree *	*	*
4. In HashSet library, clear() is never immediately followed by clone()	False	Agree Disagree *	*	*
5. In HashSet library, clear() always precedes clone()	False	Agree Disagree *	*	*
6. In HashSet library, clear() always immediately precedes clone()	False	Agree Disagree *	*	*

Question

Machine's Answer

Do you agree with machine's answer

Explain (At least 10 words)

How confident are you

1. In HashSet library, clear() is always followed by clone()

False

Agree
Disagree
*

2. In HashSet library, clear() is always immediately followed by clone()

False

Agree
Disagree
*

3. In HashSet library, clear() is never followed by clone()

False

Agree
Disagree
*

4. In HashSet library, clear() is never immediately followed by clone()

False

Agree
Disagree
*

5. In HashSet library, clear() always precedes clone()

False

Agree
Disagree
*

6. In HashSet library, clear() always immediately precedes clone()

False

Agree
Disagree
*

The API document link for library "HashSet"	java.util.HashSet
clear()	"public void clear() Removes all of the elements from this set. The set will be empty after this call returns. Specified by: clear in interface Collection Specified by: clear in interface Set Overrides: clear in class AbstractCollection"
clone()	"public Object clone() Returns a shallow copy of this HashSet instance: the elements themselves are not cloned. Overrides: clone in class Object Returns: a shallow copy of this set See Also: Cloneable"