-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
describe importing types and values #34
base: main
Are you sure you want to change the base?
Conversation
<p> | ||
Values are imported in a manner similar to functions. However, the `type` | ||
keyword must precede the name of an imported type. See here for | ||
[code showing types and values being imported](https://tour.gleam.run/standard-library/option-module/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This breaks the flow of the tour as it makes people jump forwards. All lessons should be self contained and build on previous lessons, so we'll have to show a type being imported.
I'm not sure what type would be best. Do you have any thoughts?
Thank you! I've left a note inline. |
(abandoning what I've done above)...How about if I inserted a new page called "Importing types" after the "Custom types" page in the "Data types" section? ..and change the existing titled "Unqualified imports" to "Importing functions" (leaving the content there as it's published now)? That would place the intro to |
...how about using |
Order sounds like a good idea! I don't want to change the name of the existing lesson though |
No description provided.