We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Many moons ago, some proposal or other came up for better imports. I agree it would be nice to have a better syntax, and I like the idea here. :) I had time to think about it back then, and I wrote down my thoughts here: https://github.com/chreekat/blatherings/blob/master/haskell-imports.md#alternate-proposal-2
In case 'require' ends up needing the full power of 'import' (which wouldn't surprise me), maybe the description at that link can spark ideas.
The text was updated successfully, but these errors were encountered:
Great, thanks! The idea behind require is to be as simple as possible, so you dont need that much stuff as a regular import.
But you are probably right, maybe having requires and imports in the same file would look strange.
requires
imports
This is food for thought indeed 😄
Sorry, something went wrong.
No branches or pull requests
Many moons ago, some proposal or other came up for better imports. I agree it would be nice to have a better syntax, and I like the idea here. :) I had time to think about it back then, and I wrote down my thoughts here: https://github.com/chreekat/blatherings/blob/master/haskell-imports.md#alternate-proposal-2
In case 'require' ends up needing the full power of 'import' (which wouldn't surprise me), maybe the description at that link can spark ideas.
The text was updated successfully, but these errors were encountered: