roc-lang/roc
1
1
Fork 0
mirror of https://github.com/roc-lang/roc.git synced 2024-09-22 00:09:33 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed the unqualified vs qualified function calls

Browse Source
This commit is contained in:
Salman Shaik 2022-10-26 06:00:49 +01:00
parent 35fb8df4b0
commit e9d1c2172a
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
TUTORIAL.md
View File

@ -1473,18 +1473,14 @@ Now lets import this in an *app module*:
```coffee
app 'interface-example'
packages { pf: "examples/cli/cli-platform/main.roc" }
imports [pf.Stdout, pf.Program, Parser.Core]
imports [pf.Stdout, pf.Program, Parser.Core.{ Parser, parse, sepBy1, between, ignore, flatten, sepBy }]
provides main to pf
```
Here we are importing the 'Core' module from the package 'Parser'. Now we can use functions from
the Core module by using their fully qualified names, like 'Core.flatten'.
the Core module by using their fully qualified names, like 'Parser.Core.flatten'.
This makes it clear where a certain function is from when reading through the code.
It is a convention in Roc to use fully qualified names, when using functions from other modules.
But there might be few functions/defs that are so common that they are used throughout a code base.
In such cases, we can use them with their unqualified names, by importing them as
'import [package.Module.{func1, func2}]'
## Comments
Comments that begin with `##` will be included in generated documentation (```roc docs```). They require a single space after the `##`, and can include code blocks by adding five spaces after `##`.