From 994abf93745a8f14cae35603b16917a91b0526d5 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 2 May 2026 14:24:20 +0000
Subject: [PATCH 1/3] fix: address doctest regex span and stale eslint-disable
 in `utils/constructor-name` example

The CI JavaScript lint job (run https://github.com/stdlib-js/stdlib/actions/runs/25195861572,
issue #11867) failed with two errors in `utils/constructor-name/examples/index.js`:

1. `stdlib/doctest` at line 39: "Displayed return value is `'String'`, but expected
   `undefined` instead". Root cause: the doctest rule's `RE_ANNOTATION` regex uses
   `[^;]*;` which matches any non-semicolon characters including newlines. The original
   `noop()` body contained only `// Do nothing...` with no semicolon, so the greedy
   `[^;]*` spanned from `function noop` across the function body and blank lines to
   `console.log( constructorName( 'a' ) );`, misattributing the `// => 'String'`
   annotation to the `function` identifier. Adding `return;` to the body provides a
   semicolon that terminates the greedy match inside the function, so the regex no
   longer spans past it.

2. Unused `eslint-disable-line no-buffer-constructor` at line 151. The `no-buffer-constructor`
   rule no longer fires for `new Buffer()` in this project, making the directive stale.
   Removing it eliminates the unused-directive error.

Failing run: https://github.com/stdlib-js/stdlib/actions/runs/25195861572
---
 .../@stdlib/utils/constructor-name/examples/index.js          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
index 85b4a4164250..32c97265451e 100644
--- a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
+++ b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
@@ -38,7 +38,7 @@ var Symbol = require( '@stdlib/symbol/ctor' );
 var constructorName = require( './../lib' );
 
 function noop() {
-	// Do nothing...
+	return;
 }
 
 console.log( constructorName( 'a' ) );
@@ -148,7 +148,7 @@ console.log( constructorName( new Float64Array() ) );
 console.log( constructorName( new ArrayBuffer() ) );
 // => 'ArrayBuffer'
 
-console.log( constructorName( new Buffer( 'beep' ) ) ); // eslint-disable-line no-buffer-constructor
+console.log( constructorName( new Buffer( 'beep' ) ) );
 // => 'Buffer'
 
 console.log( constructorName( Math ) );

From 75ccb98e0e837502388d9827c6c0b452d9f4cfd8 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 2 May 2026 14:36:22 +0000
Subject: [PATCH 2/3] fix: restore `// Do nothing...` comment in noop to match
 stdlib convention

Reviewer C (style) flagged that removing the `// Do nothing...` comment
deviated from the established stdlib noop convention in example files.
Restore the comment and keep `return;` below it so the function body
preserves convention while still providing the semicolon that terminates
the doctest regex's greedy `[^;]*` match inside the function.
---
 .../@stdlib/utils/constructor-name/examples/index.js             | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
index 32c97265451e..979eb5a482d7 100644
--- a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
+++ b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
@@ -38,6 +38,7 @@ var Symbol = require( '@stdlib/symbol/ctor' );
 var constructorName = require( './../lib' );
 
 function noop() {
+	// Do nothing...
 	return;
 }
 

From 43b40a5db3e26ecdd8b0eb071ef0d5e341ab7d59 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 2 May 2026 14:42:10 +0000
Subject: [PATCH 3/3] fix: suppress no-useless-return on noop return statement

The `return;` added to break the `stdlib/doctest` regex's greedy span
triggers the `no-useless-return` rule (configured as error). Add an
inline eslint-disable-line comment to suppress it.

The `RE_ESLINT_INLINE` preprocessing in the doctest rule strips
`eslint-disable-line` comments before running `RE_ANNOTATION`, so
the doctest fix is unaffected.
---
 .../@stdlib/utils/constructor-name/examples/index.js            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
index 979eb5a482d7..d0e2a2d762ac 100644
--- a/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
+++ b/lib/node_modules/@stdlib/utils/constructor-name/examples/index.js
@@ -39,7 +39,7 @@ var constructorName = require( './../lib' );
 
 function noop() {
 	// Do nothing...
-	return;
+	return; // eslint-disable-line no-useless-return
 }
 
 console.log( constructorName( 'a' ) );