<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Whoa. Everyone seems to be in favor of this. Don't you guys always return something ‘just in case’, in the best traditions of C API design? I tend to have lots of discardable results and only a few where I might legitimately forget to use it.<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">IMO, in most cases ignoring a return value is “safe”:<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">a) If a method is called only for its result, forgetting to use the result won't really introduce any new bugs — if you're not using that missing result elsewhere, storing it into a variable won't help.<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">b) If you're calling a method for its side effect, normally the result may be discarded.<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">The only case where this matters is when the method establishes a long-term relationship (like a subscription) that needs to be stored to survive. That seems like a rare case.<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">Any other practical cases?<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">A.</div>
<div style="font-family:Arial;"> </div>
</body>
</html>