Skip to content

Don't imply that a compilation unit name is a filename #1233

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

Open
jskeet opened this issue Dec 11, 2024 · 1 comment
Open

Don't imply that a compilation unit name is a filename #1233

jskeet opened this issue Dec 11, 2024 · 1 comment
Assignees

Comments

@jskeet
Copy link
Contributor

jskeet commented Dec 11, 2024

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.

@jskeet
Copy link
Contributor Author

jskeet commented Dec 11, 2024

Rex has suggested adding "As such, the accepted spelling of a compilation unit name, and its mapping, if any, to a filename is outside the scope of this specification." to 6.1

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

No branches or pull requests

2 participants