Remove unused usings from example and exemplar #2682
ErikSchierboomAnnotations
10 warnings
|
test:
exercises/concept/hyperia-forex/HyperiaForex.cs#L1
'CurrencyAmount' defines operator == or operator != but does not override Object.Equals(object o)
|
|
test:
exercises/concept/hyperia-forex/HyperiaForex.cs#L1
'CurrencyAmount' defines operator == or operator != but does not override Object.GetHashCode()
|
|
test:
exercises/practice/bank-account/BankAccountTests.cs#L166
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L54
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L36
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L54
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L36
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L72
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L72
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|
|
test:
exercises/practice/go-counting/GoCountingTests.cs#L18
Comparing an instance of HashSet<(int, int)> with an instance of IEnumerable<(int, int)> has undefined results, because the order of items in the set is not predictable. Create a stable order for the set (i.e., by using OrderBy from Linq). (https://xunit.net/xunit.analyzers/rules/xUnit2027)
|