timers: modified comment to try/finally

[Moniarchy]

Replaced try/catch with try/finally in comments, line 744.

Fixes: #14308

Checklist

• commit message follows commit guidelines

Affected core subsystem(s)

[jasnell]

Not even sure if the comment applies any more since try blocks should be optimized now. But, in general, LGTM

[BridgeAR]

There is actually already a open PR for this: #14314

[refack]

Hello @Moniarchy and welcome. Thank for the contribution 🥇
As @BridgeAR pointed out there is an open PR to fix the comment. But there's an opportunity for you to follow up on the comments made before an remove reference to try/finally optimization. Currently the reason to use runCallback is the explicit code that triggers the callback with specific number of arguments:

node/lib/timers.js

Lines 775 to 794 in b8c142c

	function runCallback(timer) {
	const argv = timer._argv;
	const argc = argv ? argv.length : 0;
	if (typeof timer._callback !== 'function')
	return promiseResolve(timer._callback, argv[0]);
	switch (argc) {
	// fast-path callbacks with 0-3 arguments
	case 0:
	return timer._callback();
	case 1:
	return timer._callback(argv[0]);
	case 2:
	return timer._callback(argv[0], argv[1]);
	case 3:
	return timer._callback(argv[0], argv[1], argv[2]);
	// more than 3 arguments run slower with .apply
	default:
	return Function.prototype.apply.call(timer._callback, timer, argv);
	}
	}

[BridgeAR]

This got superseded by a2b6872

@Moniarchy thanks for your contribution anyway! Looking forward to your next PR.