doc: use `v new` instead of `v create`
parent
4e1a09c9f5
commit
c874a22b3b
|
@ -1567,7 +1567,7 @@ NB: Each flag must go on its own line (for now)
|
|||
You can also include C code directly in your V module. For example, let's say that your C code is located in a folder named 'c' inside your module folder. Then:
|
||||
|
||||
* Put a v.mod file inside the toplevel folder of your module (if you
|
||||
created your module with `v create` you already have v.mod file). For
|
||||
created your module with `v new` you already have v.mod file). For
|
||||
example:
|
||||
```v
|
||||
Module {
|
||||
|
|
|
@ -2,6 +2,6 @@
|
|||
|
||||
Module {
|
||||
name: 'project_with_modules_having_submodules',
|
||||
description: 'This project was created with `v create` to prevent regressions with the way V module import lookup works.',
|
||||
description: 'This project was created with `v new` to prevent regressions with the way V module import lookup works.',
|
||||
dependencies: []
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue