Infinite Recursion
See original GitHub issueI’d like to request a feature. I’m using an object in a test that has a child that refers back to the parent. This causes an infinite loop when I run the test. If there could be a way to set the number of levels of recursion, it would be very nice.
Here’s an example, in case i was not clear:
public class Parent {
public Child Child { get; set; }
}
public class Child{
public Parent Parent { get; set; }
}
var parent1 = new Parent();
parent.Child = new Child{ Parent = parent };
var parent2 = new Parent();
parent.Child = new Child{ Parent = parent };
parent1.ToExpectedObject().ShouldEqual(parent2); // <--- infinite loop
Issue Analytics
- State:
- Created 11 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
infinite recursion - Wiktionary, the free dictionary
(programming) Any recursion that continues without end. Related termsEdit · crock recursion. TranslationsEdit. ±show ...
Read more >4.8. Infinite Recursion — How to Think ...
If a recursion never reaches a base case, it will go on making recursive calls forever and the program will never terminate. This...
Read more >Recursion - Wikipedia
Recursion occurs when the definition of a concept or process depends on a simpler version of ... While this apparently defines an infinite...
Read more >Avoiding unintentional infinite recursion - Using Swift
I'm starting this thread to discuss any code analysis tools or strategies that can be used for avoiding unintentional infinite recursion.
Read more >StackOverflowError and the concept of Infinite Recursion
This method call never ends, once java realises that there is no more room in the stack, it throws the error. This concept...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
could this be released?
This has been fixed in v1.3.1.