Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to add support for using unsafe static <Type>; #67329

Closed
jcouv opened this issue Mar 16, 2023 · 2 comments · Fixed by #67344 or #68557
Closed

Need to add support for using unsafe static <Type>; #67329

jcouv opened this issue Mar 16, 2023 · 2 comments · Fixed by #67344 or #68557
Assignees
Milestone

Comments

@jcouv
Copy link
Member

jcouv commented Mar 16, 2023

As part of the PR tightening the compiler enforcement on pointer types (they must always appear in unsafe context after C# 12), this scenario surfaced.
It needs confirmation from LDM and will require a parser change.

Relates to feature "alias any type" (test plan: #56323)

This issue is referenced in tests.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 16, 2023
@jcouv jcouv removed the untriaged Issues and PRs which have not yet been triaged by a lead label Mar 16, 2023
@jcouv jcouv added this to the C# 12.0 milestone Mar 16, 2023
@AlekseyTs
Copy link
Contributor

It looks like there are still references to the issue in tests. Perhaps, scenarios should be adjusted if the feature is supported now.

@AlekseyTs AlekseyTs reopened this May 9, 2023
@AlekseyTs
Copy link
Contributor

@CyrusNajmabadi Just an FYI, I re-activated this issue because it looks like there still some work needed in tests that explicitly reference this issue in comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants