From 6023a46cb30ac788ace35632df6cd4646145db4d Mon Sep 17 00:00:00 2001 From: s-ol Date: Thu, 21 May 2020 18:16:16 +0200 Subject: rename alv.builtin to alv.builtins --- docs/gen/index | 2 +- docs/internals/extensions.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/gen/index b/docs/gen/index index 55dd1df..dff601a 100755 --- a/docs/gen/index +++ b/docs/gen/index @@ -43,7 +43,7 @@ spit OUT, layout h2 a "builtins", href: '#builtins' p "These definitions are automatically loaded into the global Scope of every alive session." - ul for key, val in opairs (require 'alv.builtin').values + ul for key, val in opairs (require 'alv.builtins').values li render key, val.result } } diff --git a/docs/internals/extensions.md b/docs/internals/extensions.md index e541d9a..29cc075 100644 --- a/docs/internals/extensions.md +++ b/docs/internals/extensions.md @@ -177,7 +177,7 @@ how their arguments are evaluated. They roughly correspond to *macros* in Lisps. There is less of a concrete guideline for implementing Builtins because there are a lot more options, and it really depends a lot on what the Builtin should achieve. Nevertheless, a good starting point is to read the `Builtin` class -documentation, take a look at `Builtin`s in `alv/builtin.moon` and get +documentation, take a look at `Builtin`s in `alv/builtins.moon` and get familiar with the relevant internal interfaces (especially `AST`, `Result`, and `Scope`). -- cgit v1.2.3