Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2.0b6
2022.1
Issue ID
1355846
Regression
No
System.Memory ReadOnlySpan() method is not supported and throws an error when used
Reproduction steps:
1. Open the user's attached project
2. Observer the Console
Expected result: The are no errors in the Console
Actual result: There is an error in the Console
Reproducible with: 2021.2.0b6, 2022.1.0a5
Not reproducible with: 2020.3.16f1, 2021.1.17f1, 2021.2.0b5
could not test with: 2019.4.29f1 (downgraded project throws error)
Note:
-The error is: Assets\SpanTest.cs(26,29): error CS0570: 'ReadOnlySpan<T>.this[int].get' is not supported by the language
Comments (1)
-
SugoiDev
Aug 23, 2021 14:11
Related forum thread: https://forum.unity.com/threads/2021-2-0b6-and-system-memory-readonlyspan-under-net-4-8.1152104/
Also missing: pinning spans. So this also doesn't work
private static unsafe void SpanInFixedContext(ReadOnlySpan<byte> s) {
fixed (byte* dest = s) {
//do something
}
}Previously, we would be able to add System.Memory.dll manually, but doing so now will cause conflicts since mscorlib already includes it (even if partially).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b11