Adjust whitespace to make tests oblivious to --harmony-function-tostring

Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n

Committed: https://crrev.com/3cfd80d6a254357f90d907c89c4d16857cb06d0e
Cr-Commit-Position: refs/heads/master@{#37959}

[jwolfe, 2016-07-20 06:16:39]

Description was changed from

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n
==========

to

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n
==========

[jwolfe, 2016-07-20 06:16:40]

jwolfe@igalia.com changed reviewers:
+ littledan@chromium.org

[Dan Ehrenberg, 2016-07-21 23:48:24]

lgtm

[Dan Ehrenberg, 2016-07-21 23:48:41]

You may have to make a similar change within the Blink tests

[jwolfe, 2016-07-21 23:56:55]

The CQ bit was checked by jwolfe@igalia.com

[commit-bot: I haz the power, 2016-07-21 23:56:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-22 00:18:08]

Description was changed from

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n
==========

to

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n
==========

[commit-bot: I haz the power, 2016-07-22 00:18:09]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-22 00:18:46]

Description was changed from

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n
==========

to

==========
Adjust whitespace to make tests oblivious to --harmony-function-tostring

See discussion in https://codereview.chromium.org/2156303002/#msg8

With the new --harmony-function-tostring behavior, these tests would
fail without this change. This change makes the tests pass regardless
of whether or not --harmony-function-tostring is used.

All of these changes are simply inserting a space after the "function"
keyword to match the current function toString behavior. When
--harmony-function-tostring is enabled, the toString behavior matches
the spacing used in the function declaration. With the declaration
matching the current formatting, the toString behavior becomes
unaffected by --harmony-function-tostring.

BUG=v8:4958
LOG=n

Committed: https://crrev.com/3cfd80d6a254357f90d907c89c4d16857cb06d0e
Cr-Commit-Position: refs/heads/master@{#37959}
==========

[commit-bot: I haz the power, 2016-07-22 00:18:47]

Patchset 1 (id:??) landed as
https://crrev.com/3cfd80d6a254357f90d907c89c4d16857cb06d0e
Cr-Commit-Position: refs/heads/master@{#37959}