Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dependency to System.Memory is not needed for .NET Standard 2.1 and .NET 5.0
See original GitHub issueIn newer frameworks (.NET Standard 2.1 and .NET 5.0) Span is supported out of the box and the NuGet package is not needed.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
c# - Why does System.Memory have a dependency on ...
It seems the opposite to normal, that a newer version of .Net would require more dependencies. The System.Memory package contains libraries ...
Read more >The future of .NET Standard - .NET Blog
NET Standard, but .NET 5 and all future versions will continue to support .NET Standard 2.1 and earlier. You should think of net5.0...
Read more >Unable to resolve dependency 'System.Memory' when ...
On this another machine I tried to install nightly pre-release builds of the packages but it fails with the following error: Unable to...
Read more >System.Memory 4.5.5
Provides types for efficient representation and pooling of managed, stack, and native memory segments and sequences of such segments, ...
Read more >Unity ID
Every dependency that relies on any type inside System.Memory (or other classes that got "merged" into mscorlib) will not work, therefore ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@redwyre xxHash 1.0.7 has same changes applied. Note LZ4 still references 1.0.6 so you need to manually reference xxHash 1.0.7. I’ll change it in next release.
1.2.16 should do exactly this