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
Automatic precompilation #4931
Comments
From chohag@jtan.comJust no. Precompilation is a fine idea. Automatic precompilation is an OK idea. The no precompilation pragma is fine, and it should exist, but there needs * Not use any precompilation at all. * Not build any new precompilation files unless told to explicitly, but * Customise where exactly precompilation files are put. And while you're at it, failing to create precompilation files - eg. on a ===SORRY!=== Or this, when I touched .precomp as a file rather than a directory: ===SORRY!=== Final error: Both could prehaps elicit a warning though, unless told not to. In short: * precompilation is a cache. If a cache fails the application should * Automatic anything should always be overridable by the user, ideally Matthew [*] There is an exception to every rule, except this one. |
@coke - Status changed from 'new' to 'open' |
From @ninerI would like to close this ticket. It contains a multitude of issues, some of which have already been fixed. For example the failures to open/create files and directories. We now deal much better with permission issues. We create far fewer precomp files anyway as we can now use the precomp files created during module installation even when the user adds repositories to the chain. The process-wide means of, at run time and at rakudo's build-time to not use any precompilation at all has been talked about a lot, especially when we still had lots of issues like the mentioned permission mess. Yet despite it being a one-line change in a place that has a comment that tells the reader what to do to implement such a switch, no one has been bothered enough to actually implement it. So I assume that precompilation is nowadays working well enough for people to no longer need such a switch. |
From @ninerRejecting for the reasons listed in https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127031#txn-1420669 |
@niner - Status changed from 'open' to 'rejected' |
From kb@open.chI have the very same problem with a readonly home directory: $ perl6 To exit type 'exit' or '^D' I did not find much information about precompilation. Is it possible to do it system wide so this can be avoided? |
Migrated from rt.perl.org#127031 (status was 'rejected')
Searchable as RT127031$
The text was updated successfully, but these errors were encountered: