Visualstudio-docs: Poor documentation in CA1814
Poor documentation on the "why" of this rule.
Document Details
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 088ac03f-0e6c-9b9b-24dc-e17564a970da
- Version Independent ID: a49e1b15-68c0-896c-18a7-c7347565a387
- Content: CA1814: Prefer jagged arrays over multidimensional - Visual Studio
- Content Source: docs/code-quality/ca1814-prefer-jagged-arrays-over-multidimensional.md
- Product: visual-studio-windows
- Technology: vs-ide-code-analysis
- GitHub Login: @gewarren
- Microsoft Alias: gewarren
johnnyasantoss
All 4 comments
Edit to trigger priority labeling.
gewarren
on 27 Jul 2019
@johnnyasantoss The article states that jagged arrays use less memory space than multidimensional arrays. @mavasani Can you comment on whether this is the only reason why CA1814 recommends jagged arrays over multidimensional?
This SO post has a nice discussion of the pros and cons of each. In July 2017, one user noted that according to their calculations, in .NET Core, multi-dimensional arrays are faster than jagged arrays. If that is true, should we get rid of CA1814?
gewarren
on 27 Jul 2019
Updated content links
Mikejo5000
on 16 Dec 2020
Moved issue to .NET
Closing this in favor of https://github.com/dotnet/docs/issues/22047
Mikejo5000
on 16 Dec 2020
Related issues
Crono1981
·
3Comments
jnpwly
·
3Comments
wittelw
·
3Comments
suhailmahmood
·
3Comments
rlundy
·
3Comments
Most helpful comment
@johnnyasantoss The article states that jagged arrays use less memory space than multidimensional arrays. @mavasani Can you comment on whether this is the only reason why CA1814 recommends jagged arrays over multidimensional?
This SO post has a nice discussion of the pros and cons of each. In July 2017, one user noted that according to their calculations, in .NET Core, multi-dimensional arrays are faster than jagged arrays. If that is true, should we get rid of CA1814?