// Test user boost
        item.setUserBoost(2.0f);
        assertEquals(2.0f, item.getUserBoost(), 0.001f);

        // Test readings
        String[][] newReadings = { { "read1", "read2" }, { "read3" } };
        item.setReadings(newReadings);
        assertArrayEquals(newReadings, item.getReadings());

        // Test fields
        String[] fields = { "field1", "field2" };

These are issues that we believe are particularly well suited for outside
contributions, often because we probably won't get to them right now. If you
decide to start on an issue, leave a comment so that other people know that
you're working on it. If you want to help out, but not alone, use the issue
comment thread to coordinate.

### Contribution guidelines and standards

	XVMODW		X3, X2, X1	// 410ce374
	XVMODV		X3, X2, X1	// 418ce374
	XVMODBU		X3, X2, X1	// 410ce674
	XVMODHU		X3, X2, X1	// 418ce674
	XVMODWU		X3, X2, X1	// 410ce774
	XVMODVU		X3, X2, X1	// 418ce774

	// [X]VF{SQRT/RECIP/RSQRT}{F/D} instructions
	VFSQRTF		V1, V2		// 22e49c72
	VFSQRTD		V1, V2		// 22e89c72
	VFRECIPF	V1, V2		// 22f49c72
	VFRECIPD	V1, V2		// 22f89c72
	VFRSQRTF	V1, V2		// 22049d72
	VFRSQRTD	V1, V2		// 22089d72

package, such as C.puts. It collects all such identifiers. The next
step is to determine each kind of name. In C.xxx the xxx might refer
to a type, a function, a constant, or a global variable. Cgo must
decide which.

The obvious thing for cgo to do is to process the preamble, expanding
#includes and processing the corresponding C code. That would require
a full C parser and type checker that was also aware of any extensions

    # Overriding eigen strong inline speeds up the compiling of
    # conv_grad_ops_3d.cc and conv_ops_3d.cc by 20 minutes,
    # but this also hurts the performance. Let users decide what they want.
    write_to_bazelrc('build --define=override_eigen_strong_inline=true')


def config_info_line(name, help_text):
  """Helper function to print formatted help text for Bazel config options."""