-
Notifications
You must be signed in to change notification settings - Fork 428
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
Limit filename length for proper functioning #12770
Conversation
Hi @dgarvit: Thanks for tackling this. Unfortunately, I'm still getting failures for long filenames:
|
Seems like the building procedure is not the same in the 2 scenarios. I used the |
Interesting. I think you must be correct that it depends on the back-end tools used. My settings are:
and the output when compiling with
|
It would be nice to move this error earlier in the compile cycle. We know the file names as early as parsing, so why wait until codegen to error out? I think the error should be moved up to before the file is parsed. On a long compile this could save a lot of frustration. |
@bradcray so what we basically need to know is the maximum length of the extension possible. From the example you mentioned, it seems to be 14 (which i m guessing might just be the highest), though we'd have to discover all other possibilities to be sure. Can you help me with how I can do that? |
I don't have any insight into how to make this airtight short of doing some Google research (e.g., "what is the longest extension a compiler / linker may want to add to my filename?"). I also don't think there's great harm in being slightly conservative in filename length (i.e., I don't think it'll be the case that people frequently want to have filenames longer than 40 characters). That said, the closer we could get to the actual limit, the better. |
I'm going to close this PR since it didn't work for me and hasn't continued to receive attention. Would be happy to see someone pick it up and run with it more, but I also don't think it's holding anything important up. |
Fixes #8758.