dotnet / dotnet/csharpstandard
Don't imply that a compilation unit name is a filename
Open
- Dominant language
- C#
- Stars
- 815
- Forks
- 99
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 16
Description
In #1120, we've acknowledged that `#line` can introduce a compilation unit name which isn't a valid filename. We believe there are places which imply/assume that a compilation unit name *is* a valid filename - we should stop doing so.
Assigned to @Nigel-Ecma for some examples.
Contributor guide
Assessment
This issue has not been assessed yet.