Skip to content

Conversation

@nikomatsakis
Copy link
Contributor

This is particularly important for deeply nested types, which generate deeply nested impls. This is a fix for #19318. It's possible we could also improve this particular case not to increment the recursion count, but it's worth being able to adjust the recursion limit anyhow.

cc @jdm
r? @pcwalton

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can shrink this tower a bit with if let.

@nikomatsakis nikomatsakis force-pushed the recursion-limit branch 3 times, most recently from 920f582 to ca71e1d Compare December 4, 2014 18:35
@nikomatsakis
Copy link
Contributor Author

@sfackler done

bors added a commit that referenced this pull request Dec 9, 2014
This is particularly important for deeply nested types, which generate deeply nested impls. This is a fix for #19318. It's possible we could also improve this particular case not to increment the recursion count, but it's worth being able to adjust the recursion limit anyhow.

cc @jdm 
r? @pcwalton
@bors bors closed this Dec 9, 2014
@bors bors merged commit 34812b8 into rust-lang:master Dec 9, 2014
@brson
Copy link
Contributor

brson commented Dec 12, 2014

I'm surprised this went in without more visibility since it's a source-level interface that has to be specced and maintained. It's also tied to compiler implementation details.

bors added a commit that referenced this pull request Aug 25, 2015
@nikomatsakis nikomatsakis deleted the recursion-limit branch March 30, 2016 16:16
lnicola pushed a commit to lnicola/rust that referenced this pull request Apr 28, 2025
fix: Fix a bug in orphan rules calculation
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.

6 participants