chore: sync with poolifier repo

Signed-off-by: Jérôme Benoit <[email protected]>

Author: jerome-benoit

.serena/.gitignore

@@ -0,0 +1 @@
+/cache

.serena/memories/code_style_conventions.md

@@ -0,0 +1,50 @@
+# Code Style and Conventions
+
+## TypeScript/JavaScript Conventions
+
+- **Imports**: Use `.ts` extensions for TypeScript imports, relative paths from
+  `src/`
+- **Naming**:
+  - camelCase for variables and functions
+  - PascalCase for classes, types, enums, interfaces
+- **Types**: Explicit types over `any`, use type guards, avoid non-null
+  assertions (`!`)
+- **Async**: Prefer async/await over raw Promises, handle rejections with
+  try/catch
+- **Error Handling**: Use typed errors with structured properties
+
+## Formatting (Deno fmt)
+
+- 2-space indentation
+- Single quotes for strings
+- No semicolons
+- Trailing commas (ES5 style)
+
+## JSDoc Comments
+
+- All functions should have proper JSDoc comments
+- Include meaningful descriptions for the function purpose
+- Document all parameters with `@param {type} name - description`
+- Document return values with `@returns {type} description`
+- Empty comments like `/**  */` should be filled with proper documentation
+
+## Worker Patterns
+
+- Use MessageChannel/MessagePort for worker communication
+- Use postMessage/onmessage for worker messaging
+- Store Promise resolvers in Maps for async operations
+
+## Testing
+
+- Use `@std/expect` and `@std/testing/bdd`
+- Test files should have `.mjs` extension
+- Test files should be in `tests/` directory
+
+## Architecture Principles
+
+- Follow DRY principle (Don't Repeat Yourself)
+- Maintain single source of truth for configuration
+- Use design patterns (factory/strategy) where appropriate
+- Optimize for minimal time/space complexity
+- English-only code and documentation
+- Tests-first mindset

.serena/memories/codebase_structure.md

@@ -0,0 +1,41 @@
+# Codebase Structure
+
+## Root Directory Structure
+
+```
+/
+├── src/                    # Main source code
+│   ├── pools/             # Pool implementations and strategies
+│   ├── queues/            # Queue implementations
+│   ├── worker/            # Worker abstractions and implementations
+│   └── mod.ts             # Main module exports
+├── tests/                 # Test files (.mjs extension)
+├── examples/              # Usage examples for different runtimes
+│   ├── deno/             # Deno-specific examples
+│   └── bun/              # Bun-specific examples
+├── benchmarks/           # Performance benchmarks
+├── docs/                 # Documentation files
+├── dist/                 # Built/bundled files
+├── .github/              # GitHub workflows and configs
+└── deno.json             # Deno configuration
+
+## Key Source Files
+- `src/mod.ts` - Main entry point with exports
+- `src/pools/abstract-pool.ts` - Base pool implementation
+- `src/pools/thread/fixed.ts` - Fixed thread pool
+- `src/pools/thread/dynamic.ts` - Dynamic thread pool
+- `src/worker/abstract-worker.ts` - Base worker class
+- `src/worker/thread-worker.ts` - Thread worker implementation
+
+## Architecture Patterns
+- Factory pattern for pool creation
+- Strategy pattern for worker selection
+- Observer pattern for pool events
+- Template method pattern for abstract classes
+
+## Module Organization
+- Each module has clear separation of concerns
+- Types are defined in separate files or alongside implementations
+- Utilities are separated from core logic
+- Test files mirror source structure in tests/ directory
+```

.serena/memories/project_overview.md

@@ -0,0 +1,33 @@
+# Poolifier Web Worker Project Overview
+
+## Purpose
+
+Poolifier Web Worker is a TypeScript/JavaScript library that provides worker
+pool implementations for Deno, Bun, and browser environments using the Web
+Worker API. It enables CPU and/or I/O intensive task execution without blocking
+the main event loop.
+
+## Key Features
+
+- Fixed and dynamic pool size management
+- Worker choice strategies for task distribution
+- Lockless task queueing and rescheduling
+- Support for sync/async task functions
+- Multiple task functions with priority queuing
+- Error handling and performance monitoring
+- Zero runtime dependencies
+
+## Tech Stack
+
+- **Runtime**: Deno, Bun, Browser
+- **Language**: TypeScript with ESM modules
+- **Testing**: Deno test framework with @std/expect
+- **Benchmarking**: Tatami-ng and built-in Deno bench
+- **Formatting**: Deno fmt (2-space, single quotes, no semicolons)
+- **Linting**: Deno lint
+
+## Target Platforms
+
+- Deno >= 1.40.x
+- Bun >= 1.x
+- Modern browsers with Web Worker support

.serena/memories/suggested_commands.md

@@ -0,0 +1,34 @@
+# Suggested Commands for Poolifier Web Worker
+
+## Development Commands
+
+- `deno task test` - Run all tests
+- `deno task test:parallel` - Run tests in parallel
+- `deno task test:coverage` - Run tests with coverage
+- `deno test -A tests/path/to/specific.test.mjs` - Run single test file
+- `deno task lint` - Run linting checks
+- `deno task lint:fix` - Run linting with auto-fixes
+- `deno task format` - Format code
+- `deno task format:check` - Check formatting without fixing
+- `deno task bundle` - Bundle the project
+- `deno task coverage:report` - Generate coverage report
+
+## Benchmarking Commands
+
+- `deno task benchmark:deno` - Run Deno benchmarks
+- `deno task benchmark:tatami-ng` - Run Tatami-ng benchmarks
+- `deno task benchmark:tatami-ng:debug` - Run benchmarks with debugging
+
+## Documentation
+
+- `deno task documentation` - Generate code documentation
+
+## Utilities
+
+- `git` - Git version control
+- `ls` - List files
+- `cd` - Change directory
+- `grep` - Search text patterns
+- `find` - Find files
+- `cat` - Display file content
+- `head`/`tail` - Show beginning/end of files

.serena/memories/task_completion_checklist.md

@@ -0,0 +1,45 @@
+# Task Completion Checklist
+
+## When a Task is Completed
+
+### 1. Code Quality Checks
+
+- Run `deno task lint` to check for linting issues
+- Run `deno task lint:fix` to auto-fix linting issues
+- Run `deno task format` to format code consistently
+
+### 2. Testing
+
+- Run `deno task test` to execute all tests
+- For specific changes, run individual test files:
+  `deno test -A tests/path/to/specific.test.mjs`
+- If making significant changes, run `deno task test:coverage` to ensure
+  coverage
+
+### 3. Documentation
+
+- Ensure all new functions have proper JSDoc comments
+- Update documentation if public API changes
+- Generate code documentation with `deno task documentation` if needed
+
+### 4. Final Validation
+
+- Verify code builds: `deno task bundle`
+- Check format compliance: `deno task format:check`
+- Ensure no linting errors: `deno task lint`
+
+### 5. Quality Gates
+
+All of the following must pass before considering a task complete:
+
+- ✅ Linting passes
+- ✅ Formatting is correct
+- ✅ All tests pass
+- ✅ Code coverage is maintained
+- ✅ Documentation is updated
+
+### 6. Git Workflow
+
+- Stage relevant changes: `git add <files>`
+- Commit with meaningful message: `git commit -m "description"`
+- Push changes: `git push`

.serena/project.yml

@@ -0,0 +1,84 @@
+# list of languages for which language servers are started; choose from:
+#   al               bash             clojure          cpp              csharp           csharp_omnisharp
+#   dart             elixir           elm              erlang           fortran          go
+#   haskell          java             julia            kotlin           lua              markdown
+#   nix              perl             php              python           python_jedi      r
+#   rego             ruby             ruby_solargraph  rust             scala            swift
+#   terraform        typescript       typescript_vts   zig
+# Note:
+#   - For C, use cpp
+#   - For JavaScript, use typescript
+# Special requirements:
+#   - csharp: Requires the presence of a .sln file in the project folder.
+# When using multiple languages, the first language server that supports a given file will be used for that file.
+# The first language is the default language and the respective language server will be used as a fallback.
+# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
+languages:
+  - typescript
+
+  # the encoding used by text files in the project
+  # For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
+encoding: 'utf-8'
+
+# whether to use the project's gitignore file to ignore files
+# Added on 2025-04-07
+ignore_all_files_in_gitignore: true
+
+# list of additional paths to ignore
+# same syntax as gitignore, so you can use * and **
+# Was previously called `ignored_dirs`, please update your config if you are using that.
+# Added (renamed) on 2025-04-07
+ignored_paths: []
+
+# whether the project is in read-only mode
+# If set to true, all editing tools will be disabled and attempts to use them will result in an error
+# Added on 2025-04-18
+read_only: false
+
+# list of tool names to exclude. We recommend not excluding any tools, see the readme for more details.
+# Below is the complete list of tools for convenience.
+# To make sure you have the latest list of tools, and to view their descriptions,
+# execute `uv run scripts/print_tool_overview.py`.
+#
+#  * `activate_project`: Activates a project by name.
+#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
+#  * `create_text_file`: Creates/overwrites a file in the project directory.
+#  * `delete_lines`: Deletes a range of lines within a file.
+#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
+#  * `execute_shell_command`: Executes a shell command.
+#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
+#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
+#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
+#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
+#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
+#  * `initial_instructions`: Gets the initial instructions for the current project.
+#     Should only be used in settings where the system prompt cannot be set,
+#     e.g. in clients you have no control over, like Claude Desktop.
+#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
+#  * `insert_at_line`: Inserts content at a given line in a file.
+#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
+#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
+#  * `list_memories`: Lists memories in Serena's project-specific memory store.
+#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
+#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
+#  * `read_file`: Reads a file within the project directory.
+#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
+#  * `remove_project`: Removes a project from the Serena configuration.
+#  * `replace_lines`: Replaces a range of lines within a file with new content.
+#  * `replace_symbol_body`: Replaces the full definition of a symbol.
+#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
+#  * `search_for_pattern`: Performs a search for a pattern in the project.
+#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
+#  * `switch_modes`: Activates modes by providing a list of their names
+#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
+#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
+#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
+#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
+excluded_tools: []
+
+# initial prompt for the project. It will always be given to the LLM upon activating the project
+# (contrary to the memories, which are loaded on demand).
+initial_prompt: ''
+
+project_name: 'poolifier-web-worker'
+included_optional_tools: []

examples/deno/javascript/multiFunctionWorker.js

@@ -1,10 +1,20 @@
 import { ThreadWorker } from '@poolifier/poolifier-web-worker'
 
+/**
+ * First worker function example.
+ * @param data - The input data containing text.
+ * @returns The processed result with modified text.
+ */
 function fn0(data) {
   console.info('Executing fn0')
   return { data: `fn0 input text was '${data.text}'` }
 }
 
+/**
+ * Second worker function example.
+ * @param data - The input data containing text.
+ * @returns The processed result with modified text.
+ */
 function fn1(data) {
   console.info('Executing fn1')
   return { data: `fn1 input text was '${data.text}'` }

examples/deno/javascript/yourWorker.js

@@ -1,5 +1,9 @@
 import { ThreadWorker } from '@poolifier/poolifier-web-worker'
 
+/**
+ * Example worker function that performs JSON serialization operations.
+ * @returns The result indicating successful completion.
+ */
 function yourFunction() {
   for (let i = 0; i <= 1000; i++) {
     const o = {

src/circular-buffer.ts

@@ -16,7 +16,10 @@ export class CircularBuffer {
   public size: number
 
   /**
-   * @param size - Buffer size. @defaultValue defaultBufferSize
+   * CircularBuffer constructor.
+   *
+   * @param size - Buffer size.
+   * @defaultValue defaultBufferSize
    * @returns CircularBuffer.
    */
   constructor(size: number = defaultBufferSize) {