Fix clang build after r12956

Fix clang build after r12956

That change added a test which called the handlified version of JSObject::SetElement and didn't check the return value, but that method has a MUST_USE_RESULT annotation. This change removes the annotation for consistency with other handlified static methods (like SetProperty).

Committed: https://code.google.com/p/v8/source/detail?r=12963

[Yang, 2012-11-14 20:01:32]

On 2012/11/14 18:40:35, adamk wrote:

I'd prefer using the USE macro at the point where the return value is not used
(the test you mentioned). Would that be viable?

[Yang, 2012-11-14 20:02:46]

On 2012/11/14 20:01:32, Yang wrote:
> On 2012/11/14 18:40:35, adamk wrote:
> 
> I'd prefer using the USE macro at the point where the return value is not used
> (the test you mentioned). Would that be viable?

LGTM. Landing.

[adamk, 2012-11-14 20:04:34]

On 2012/11/14 20:01:32, Yang wrote:
> On 2012/11/14 18:40:35, adamk wrote:
> 
> I'd prefer using the USE macro at the point where the return value is not used
> (the test you mentioned). Would that be viable?

Seems unnecessary to force people to use the result if it's a handle; as I said,
that's not consistent with other handlified methods. I assumed the reason for
MUST_USE_RESULTs in objects.h was for functions that could return GC Failures.