Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

rust-lang / rust Public

Notifications You must be signed in to change notification settings
Fork 13.3k
Star 103k

Code
Issues 5k+
Pull requests 749
Actions
Projects 9
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Only run dataflow for const qualification if type-based check would fail#71330

Merged

bors merged 4 commits intorust-lang:masterrust-lang/rust:masterfrom

ecstatic-morse:const-qualif-lazyecstatic-morse/rust:const-qualif-lazyCopy head branch name to clipboard

Apr 25, 2020

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Apr 23, 2020

Make type alias private
ecstatic-morse
committed
Don't cache result of `in_any_value_of_ty` for locals
ecstatic-morse
committed
Lazily run dataflow for const qualification
ecstatic-morse
committed
Cycle errors now occur during const-eval, not checking
ecstatic-morse
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.