Norns faq.git #116
Merged
Norns faq.git #116
Conversation
|
awesome. fwiw i wonder if adding something about how lookup works (and differs) might not be useful down the road? and maybe a forward pointer to the language guide needless to say, this is already useful... i say ship it! :) |
|
|
||
| - `require()` looks in more places - see `norns/lua/core/config.lua` | ||
|
|
||
| - most importantly, `require()` caches its results, and will not re-run its arguments (unless you use a hack[^1]) the state of a `require`'d module is persisted, and this is significant. consider the following set of files. |
pq
Aug 8, 2019
Collaborator
perhaps move the paren?
=>
most importantly, require() caches its results, and will not re-run its arguments (unless you use a hack[^1] the state of a require'd module is persisted), and this is significant.
perhaps move the paren?
=>
most importantly, require() caches its results, and will not re-run its arguments (unless you use a hack[^1] the state of a require'd module is persisted), and this is significant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
this isn't perfect but it's a start maybe?