If you try throwing an error from an implementation of renderRow or renderSectionHeader in a ListView, you get a very cryptic error message with a stack trace that doesn't point to the problematic code at all.
A similar problem also occurs if either of those methods returns undefined.
It would be good if those weren't so cryptic (maybe wrapped in a try/catch?).