-
Notifications
You must be signed in to change notification settings - Fork 132
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
Reinstate spago script
#1000
Comments
This may require changes in |
This should now be unblocked? |
Yes and no. For Linux/Mac, this is unblocked. For Windows, this is unblocked but may not work correctly in all cases. In |
Do we know why that 150? Is that just a number that is deemed "good enough" to read all the shebang lines? |
AFAICT, yes. That's what was in the original code. I can't recall whether there was a comment explaining why. |
150 chars should be quite enough for the majority of cases, we can try shipping this and come back to bump it if we ever figure out it's not enough |
It's your call. |
Let's |
A question/proposal: instead of (or in addition to) specifying package set and dependencies on the command line, how about supporting them via pragmas in the file itself? Haskell Stack does that to an extent, but I don't like the command-line syntax, I think F# does it much better. And speaking of F#: it has another pragma |
I don't have a strong opinion on this, except for the fact that whatever we add in |
Yes, of course, the pragmas would look like comments to the compiler. The Haskell patch was for shebang lines, not the pragmas. Pragmas in Haskell files are also just comments, no patch would be needed for them. And while I wasn't actually proposing to support shebangs as well, it can also be easily done: as long as we're copying the files to a different location anyway, we can just cut off the shebang lines along the way. |
Still needs to be ported from the Haskell implementation, see here
The text was updated successfully, but these errors were encountered: