Skip to content

Conversation

KushagraSikka
Copy link

Enhanced IPv4Address documentation with comprehensive examples and parameter descriptions - Improved error messages in NetworkAddressError with actionable guidance - Added detailed documentation for CIDRAddress including usage examples and method descriptions - Expanded AsyncLock documentation with use cases and threading safety information - Enhanced Timeout documentation with implementation details and performance notes - Improved error message clarity in Timeout.swift by replacing generic fatalError These changes make the API more accessible to new contributors and provide better developer experience through clear error messages and comprehensive documentation.

KushagraSikka and others added 2 commits June 17, 2025 07:26
…tras - Enhanced IPv4Address documentation with comprehensive examples and parameter descriptions - Improved error messages in NetworkAddressError with actionable guidance - Added detailed documentation for CIDRAddress including usage examples and method descriptions - Expanded AsyncLock documentation with use cases and threading safety information - Enhanced Timeout documentation with implementation details and performance notes - Improved error message clarity in Timeout.swift by replacing generic fatalError These changes make the API more accessible to new contributors and provide better developer experience through clear error messages and comprehensive documentation.
@dcantah
Copy link
Member

dcantah commented Jun 17, 2025

Are these mostly copies of what's already in #148?

@KushagraSikka
Copy link
Author

Hi @dcantah — great catch and thanks for reviewing!

You’re absolutely right: this PR (#147) contains the same documentation changes already included in #148. The key difference is that #148 also adds:
• Full unit test coverage for AsyncLock and Timeout (420+ lines)
• Swift 6.2–compliant test implementations
• Additional fixes for concurrency/type safety in tests

I initially opened this PR to separate the doc/error message improvements, but ultimately included them in #148 as well to keep the test coverage self-contained and traceable to the updated APIs.

Feel free to close this one in favor of #148 if you prefer a single merge path — happy to streamline however you see fit!

@dcantah dcantah closed this Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants