]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: e3048c7 50f29d4)
Rollup merge of #104252 - faern:stabilize-const_socketaddr, r=JohnTitor
authorMatthias Krüger <matthias.krueger@famsik.de>
Sat, 28 Jan 2023 10:11:06 +0000 (11:11 +0100)
committerGitHub <noreply@github.com>
Sat, 28 Jan 2023 10:11:06 +0000 (11:11 +0100)
commit36ef4f15d3eb03d6a99657d13ef06209263c2cf9
treebe456720f313b28db95ef1cfe291a716e6dd6cc3tree | snapshot
parente3048c78384d1cd7b70a0bb122d385cb67eeb06fcommit | diff
parent50f29d48bd5fb17b7b1669b842aba89bbe9bef6dcommit | diff
Rollup merge of #104252 - faern:stabilize-const_socketaddr, r=JohnTitor

Stabilize the const_socketaddr feature

Stabilizes `#![feature(const_socketaddr)]`. Tracking issue: #82485
Closes #82485

This has been unstably const for over a year now. And the code change simplifying the constness of the `new` constructors has been in stable Rust since 1.64 (a bit over a full release cycle). I'm not aware of any blockers to this stabilization.
Empowering everyone to build reliable and efficient software.