Use V8 Maybe APIs in extensions/renderer

Use V8 Maybe APIs in extensions/renderer

Replacing DEPRECATE_SOON APIs.

BUG=479065

[bashi, 2015-06-09 03:57:13]

Patchset #1 (id:1) has been deleted

[bashi, 2015-06-09 08:22:12]

bashi@chromium.org changed reviewers:
+ jochen@chromium.org, kalman@chromium.org

[bashi, 2015-06-09 08:22:12]

PTAL?

Context:
https://groups.google.com/forum/#!searchin/v8-users/maybe/v8-users/gQVpp1Hmbq...

[not at google - send to devlin, 2015-06-09 20:08:20]

I'll get to this as soon as possible, but I notice it's quite a large diff:

(+629 lines, -342 lines)

is it possible to break it along some sort of logical lines, like one to do
trivial renames, and other(s) to do logic fixes like you've done for checking
string lengths and so on? That will make identifying any failures more easily -
in my experience, changing v8 API code is quite fragile, and this is a big
change.

[not at google - send to devlin, 2015-06-09 20:28:41]

in particular it would be good to do some of the complex classes like module
system and messaging in completely separate CLs because they're complex.

[bashi, 2015-06-09 22:38:03]

On 2015/06/09 20:28:41, kalman wrote:
> in particular it would be good to do some of the complex classes like module
> system and messaging in completely separate CLs because they're complex.

Thank you for taking a look! I'll create separate CLs (I'm ooo several days so
it may take time).