perf: reuse SecureRandom instance in MockLnServer #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses performance feedback from PR #57:
SecureRandominstantiation on every invoice generation is expensive.Changes
SecureRandoma static final field instead of creating new instances ingenerateValidBolt11Invoice()target/directories, not just root-levelSecureRandomis thread-safe and initialization involves entropy gathering, making this a meaningful optimization for high-throughput scenarios.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.