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
Describe the bug
Attempting to search for null in a SkipList results in the application crashing due to a NullReferenceException
To Reproduce
Steps to reproduce the behavior:
Create a new SkipList<string> var skipList = new SkipList<string>():
Try to search for null list.Contains(null)
Expected behavior
I expected this SkipList to have the same behaviour as the standard C# List implementation when processing null. Applying the same steps to a standard C# List will result in list.Contains(null) evaluating to false without crashing.
Environment:
OS: Windows 10 Home (Version 10.0.18362 Build 18362)
.NET Version: .NET Core v3.1.101
IDE: Microsoft Visual Studio Community 2019 - Version 16.4.5
Additional context
Bug can be reproduced with any of the functions that make use of the SkipList's built-in comparator: Remove, Find, Contains, etc.
The text was updated successfully, but these errors were encountered:
Gutsonok
added a commit
to Gutsonok/C-Sharp-Algorithms
that referenced
this issue
Aug 8, 2020
Describe the bug
Attempting to search for null in a SkipList results in the application crashing due to a NullReferenceException
To Reproduce
Steps to reproduce the behavior:
var skipList = new SkipList<string>():
list.Contains(null)
Expected behavior
I expected this SkipList to have the same behaviour as the standard C# List implementation when processing null. Applying the same steps to a standard C# List will result in
list.Contains(null)
evaluating to false without crashing.Environment:
OS: Windows 10 Home (Version 10.0.18362 Build 18362)
.NET Version: .NET Core v3.1.101
IDE: Microsoft Visual Studio Community 2019 - Version 16.4.5
Additional context
Bug can be reproduced with any of the functions that make use of the SkipList's built-in comparator: Remove, Find, Contains, etc.
The text was updated successfully, but these errors were encountered: