diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-24 19:39:13 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-24 19:39:13 +0200 |
| commit | a20e7ffdb1a11368cecf18db703d10d6e8533081 (patch) | |
| tree | 321d825bfab39bbcfb5d0f6ad444bd53b6aa1982 /compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs | |
| parent | f61306d47bc98af8bb9d15f1adf6086785590a8c (diff) | |
| parent | 0e5c5a25961a94d866a65bb956d5ae9bf7c84eef (diff) | |
| download | rust-a20e7ffdb1a11368cecf18db703d10d6e8533081.tar.gz rust-a20e7ffdb1a11368cecf18db703d10d6e8533081.zip | |
Rollup merge of #131790 - nmathewson:doc_socketaddr_representation, r=tgross35
Document textual format of SocketAddrV{4,6}
This commit adds new "Textual representation" documentation sections to SocketAddrV4 and SocketAddrV6, by analogy to the existing "textual representation" sections of Ipv4Addr and Ipv6Addr.
Rationale: Without documentation about which formats are actually accepted, it's hard for a programmer to be sure that their code will actually behave as expected when implementing protocols that require support (or rejection) for particular representations. This lack of clarity can in turn can lead to ambiguities and security problems like those discussed in RFC 6942.
(I've tried to describe the governing RFCs or standards where I could, but it's possible that the actual implementers had something else in mind. I could not find any standards that corresponded _exactly_ to the one implemented in SocketAddrv6, but I have linked the relevant documents that I could find.)
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs')
0 files changed, 0 insertions, 0 deletions