You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a bug in the compiler, but during extension development, I symlinked an extension to the correct location (from my repo, which was elsewhere on my system) and it wasn't recognized during compilation. The same error also occurred when I symlinked an interpreter directory in the *.materials/Templates subfolder.
The text was updated successfully, but these errors were encountered:
It may arise because the code in Directories::listing(P) in Chapter 3 of the foundation module does not distinguish between symlinks and regular files. It's not altogether easy to change that assumption, though, because the users of this function assume that they can form a valid path by forming P/leafname on any leafname they find as a result of running, in effect, readdir on P. I might still expect that to work, though, if the symlink is sensibly named? Presumably fopen, for example, works when given a path that goes through a symlink?
I'm not sure what if anything it's sensible to do about this.
This might be a bug in the compiler, but during extension development, I symlinked an extension to the correct location (from my repo, which was elsewhere on my system) and it wasn't recognized during compilation. The same error also occurred when I symlinked an interpreter directory in the
*.materials/Templates
subfolder.The text was updated successfully, but these errors were encountered: