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

C# language support status #829

Open
48 of 96 tasks
dgrunwald opened this issue Aug 27, 2017 · 3 comments
Open
48 of 96 tasks

C# language support status #829

dgrunwald opened this issue Aug 27, 2017 · 3 comments
Labels
C# Decompiler The decompiler engine itself Documentation

Comments

@dgrunwald
Copy link
Member

dgrunwald commented Aug 27, 2017

Here we list recent C# language versions (> C# 6) and their implementation status in ILSpy. Older (completed) language versions can be found in the wiki.

  • Language features that are checked are implemented in the current master branch of ILSpy and have a minimal test suite at least.
  • Language features that are crossed out will likely never be implemented in the decompiler, either because
    • they are not reproducible from compiled binaries (e.g. constant interpolated strings, Caller info attributes),
    • or they are of limited use and would require too much work to implement in the decompiler (e.g. static and global using directives, expression bodied members).

C# 11 (VS 2022 17.4)

C# 10 (VS 2022 17.0)

C# 9 (VS 2019 16.8)

C# 8.0 (Visual Studio 2019)

C# 7.3 (Visual Studio 2017 version 15.7)

C# 7.2 (Visual Studio 2017 version 15.4)

C# 7.1 (Visual Studio 2017 version 15.3)

C# 7.0 (Visual Studio 2017)

@dgrunwald dgrunwald changed the title newcompiler C# language support status newdecompiler C# language support status Aug 27, 2017
@sharwell
Copy link
Contributor

sharwell commented Aug 28, 2017

💡 I noticed you have nameof operator crossed out. While this is typically not possible due to lack of information in the compiler output, it would be good to support it in limited cases, such as the paramName argument for ArgumentException and derived types, which is likely to align with the name of a parameter visible in the current scope.

@sharwell
Copy link
Contributor

sharwell commented Aug 28, 2017

💡 I noticed you have Caller Info attributes crossed out. While this is typically not possible, one way it could be leveraged is intentionally omitting arguments (and allowing defaults to apply) in cases where the IL passes literal arguments which are known to align with the actual values that would be inserted by these attributes. The CallerMemberNameAttribute would work without additional considerations. If other information is desired, the #line directive could be used to set the file name and line number for the call site.

@siegfriedpammer siegfriedpammer changed the title newdecompiler C# language support status C# language support status Sep 25, 2017
@christophwille christophwille added this to To Do in Sticky Issues Dec 21, 2017
@christophwille christophwille moved this from To Do to In progress in Sticky Issues Dec 21, 2017
@siegfriedpammer siegfriedpammer pinned this issue Dec 16, 2018
@siegfriedpammer siegfriedpammer added C# Decompiler The decompiler engine itself Documentation labels Mar 3, 2020
@icsharpcode icsharpcode deleted a comment from abou-hafs May 17, 2021
@IanKemp
Copy link

IanKemp commented Sep 7, 2021

  • I assume struck-through indicates "won't implement"? Would be useful to have that info at the beginning of the issue.
  • For the "won't implement" features, a one-liner description or link to relevant issue discussing why not would be appreciated for additional context.
  • Consider ordering by langver descending (so C# 10 is at the start and 1 at the end) - very few people are going to be interested in the older versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C# Decompiler The decompiler engine itself Documentation
Projects
Sticky Issues
  
In progress
Development

No branches or pull requests

4 participants