Conversation
# Conflicts: # Build/JetBrains.Annotations.cs # CodeJam.Experimental.Tests/UseCases/TempDataUseCases.cs # CodeJam.Main/Arithmetic/OperatorsFactory.cs # CodeJam.Main/Assertions/Code.cs # CodeJam.Main/Assertions/CodeExceptions.cs # CodeJam.Main/Assertions/DebugCode.generated.cs # CodeJam.Main/CodeJam.Main.csproj # CodeJam.Main/Collections/SuffixTree/SuffixTreeBase.cs # CodeJam.Main/Expressions/ExpressionExtensions.cs # CodeJam.Main/Reflection/MemberAccessor.cs # CodeJam.Main/Strings/StringExtensions.cs # CodeJam.Main/Threading/ParallelQueue.cs # CodeJam.sln.DotSettings
|
Feel free to apply changes from previous PR. |
|
One more interesting point. R# automatically removes its own CanBeNull markup when adding "?" to a type. @NN--- |
|
I paid attention to that:) |
|
@andrewvk So, do we agree that all ReSharper nullability attributes will be replaced with .NET nullability attributes ? |
|
Btw, IDictionary doesn't require "TKey : notnull" according to sources. It means adding this constraint is not correct. |
Coding style fixes.
|
You mean that NUnit still doesn't have a NotNull attribute markup? Yeah, that's pretty weird. Of course, in this case it's worth adding your own variant. |
|
Yeah. I tried to reproduce this in a separate project but everything compiled. |
|
|
…into feature/nullable_v3
|
It is better to not introduce additional constraint if possble |
|
Fixed recursion and now the build works :) |



No description provided.