Cannot run samples involving records
See original GitHub issueError message: Unbreakable.AssemblyGuardException: Method System.Void Rec::Deconstruct(System.Int32&) performs pointer operations which cannot be validated.
Sample code:
using System;
Console.WriteLine(new Rec(1).X);
// ---
record Rec(int X);
namespace System.Runtime.CompilerServices { class IsExternalInit { } }
This probably happens because records with parameter lists synthesize a Deconstruct
method. Is there any way the restriction can be modified to make it possible to run some record samples?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Linux perf record not generating any samples
perf record -e cpu-clock <command>. works for me. The problem seems to be that th default event (cycles) is not available.
Read more >Service Manager - ITOM Practitioner Portal
The following is an excerpt of a sample error message indicating that no mapping configuration was found for the push TQL query. java.lang....
Read more >Troubleshooting | Apps Script
These errors are caused by using a function or class incorrectly, and can only be detected once the script has been run. For...
Read more >Dealing with errors - Power Query
In this query, you have a Sales column that has one cell with an error caused by a conversion error.
Read more >Review and troubleshoot import errors
Learn how to view and troubleshoot common errors that occur during record imports. ... The import file contains a row with data that...
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 FreeTop 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
Top GitHub Comments
Hi @Kryptos-FR, I didn’t have a chance to take a look at the root cause, however this has been resolved by moving to a new Run model.
Interesting! I will take a look when I have a moment.