Skip to content

Goals: add the restrictions update #1670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 6, 2025
Merged

Goals: add the restrictions update #1670

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions content/Project-Goals-2025-July-Update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -984,6 +984,29 @@ Chiming in for @epage here since further progress is still blocked on the compil
<!-- markdown separator -->


<details>
<summary>1 detailed update available.</summary>

<!-- this comment helps to convince the markdown parser to do the right thing -->


<!-- this comment helps to convince the markdown parser to do the right thing -->

<a href="https://github.com/rust-lang/rust-project-goals/issues/257#issuecomment-3155934755">Comment by @jhpratt posted on 2025-08-05:</a><br>

<blockquote>

<!-- this comment helps to convince the markdown parser to do the right thing -->

Implementation remains in progress; I'll be able to land a couple PRs soon getting it largely implemented. Progress was slower than expected due to me having a fair amount going on. As I still very much want this feature, I will continue work on it even with the goal having formally lapsed.

Additionally, I think that after it's fully implemented it may be feasible to leverage the crate-local knowledge of `impl` restrictions to optimize `dyn` in an `enum_dispatch`-like manner. I haven't investigated the feasibility of that in the compiler — it's merely a suspicion.

<!-- this comment helps to convince the markdown parser to do the right thing -->

</blockquote>

</details>

<!-- markdown separator -->

Expand Down