Anjali Dewangan — R51-T047: Publish a runnable example for bloom filter (BloomFilter.js) [src/data-structures/bloom-filter] #47

Student: Anjali Dewangan

Task: R51-T047 · 7 of 10
Repository: https://github.com/S-AI-Projects/javascript-algorithms
Assigned working branch: student/e26b07f0661

Goal

Work on src/data-structures/bloom-filter/BloomFilter.js. Add an executable worked example explaining bloom filter from input through intermediate state to the final result. Use the smallest valid input and one ordinary input for bloom filter from src/data-structures/bloom-filter/BloomFilter.js. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition. Fixture: Use the smallest valid input and one ordinary input for bloom filter from src/data-structures/bloom-filter/BloomFilter.js. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition.

Steps

1. Read src/data-structures/bloom-filter/BloomFilter.js, especially bloom filter near line 1. Record its public inputs, result, mutation behavior and any external dependencies before changing it.
2. Calculate the intermediate states by hand and compare them with one traced execution.
3. Use the language’s existing documentation conventions; ensure examples use the real public names and valid imports.
4. Implement work/R51-T047/check.py as a focused runner that executes the new checks and propagates failures. Native check to incorporate: run the repository test script in non-watch mode after installing from its lockfile; for browser-only code use a browser test instead of plain Node. Record the actual command and nonzero test count.
5. Create the checks specified below and run python3 work/R51-T047/check.py. Save inputs, expected versus actual results and tool versions in work/R51-T047/; a check must exit non-zero when an assertion fails.
6. Commit the repository change on branch R51-T047; prepare a PR to the organisation fork explaining the result and linking the checks. Keep each task independently reviewable. Remove work/R51-T047/ from a later upstream branch.

Done when

☐ The checked behavior is tied to bloom filter in src/data-structures/bloom-filter/BloomFilter.js; every assertion has an explicit expected value.
☐ Use the smallest valid input and one ordinary input for bloom filter from src/data-structures/bloom-filter/BloomFilter.js. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition.
☐ Existing supported behavior and the public interface are preserved unless a failing regression demonstrates and documents a defect.
☐ The documentation example is executed by a check and its displayed output is asserted.
☐ The explanation identifies the decisive state transition rather than paraphrasing every line.

Submission checklist

• Complete this task and its checks.
• Add the required evidence and link your pull request here.
• Select this S-AI-Projects fork as the PR base repository.
• Request instructor review.

Keep this PR focused on this task. Do not submit assignment PRs to the upstream repository.