Merge e4f39248f1ecfbc92d0838c220c45eec872d5dff into 8487c083e1faecb1259be8a8873618cfdb69d33d

This commit is contained in:
Kung, Li-Chieh 2024-02-27 16:46:46 -07:00 committed by GitHub
commit 0e2e36b541
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -12,7 +12,7 @@ Naming rules follow
[Microsoft's C# naming guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/naming-guidelines). [Microsoft's C# naming guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/naming-guidelines).
Where Microsoft's naming guidelines are unspecified (e.g. private and local Where Microsoft's naming guidelines are unspecified (e.g. private and local
variables), rules are taken from the variables), rules are taken from the
[CoreFX C# coding guidelines](https://github.com/dotnet/runtime/blob/master/docs/coding-guidelines/coding-style.md) [CoreFX C# coding guidelines](https://github.com/dotnet/runtime/blob/main/docs/coding-guidelines/coding-style.md)
Rule summary: Rule summary:
@ -337,7 +337,7 @@ int SomeProperty => _someProperty
* In general, prefer a named class type over `Tuple<>`, particularly when * In general, prefer a named class type over `Tuple<>`, particularly when
returning complex types. returning complex types.
### String interpolation vs `String.Format()` vs `String.Concat` vs `operator+` ### `String interpolation` vs `String.Format()` vs `String.Concat` vs `operator+`
* In general, use whatever is easiest to read, particularly for logging and * In general, use whatever is easiest to read, particularly for logging and
assert messages. assert messages.