From 724f34875cfa3c0edc5f2e021e4fe015daca5da2 Mon Sep 17 00:00:00 2001 From: Natalie Weizenbaum Date: Wed, 19 Jun 2019 14:51:18 -0700 Subject: [PATCH] [Module System] Resolve built-in global functions and mixins --- accepted/module-system.changes.md | 2 ++ accepted/module-system.md | 7 +++++++ 2 files changed, 9 insertions(+) diff --git a/accepted/module-system.changes.md b/accepted/module-system.changes.md index 582d29dc..1f3696bd 100644 --- a/accepted/module-system.changes.md +++ b/accepted/module-system.changes.md @@ -4,6 +4,8 @@ rather than after. This ensures that the clause with unbounded length comes last if both are present. +* Describe how to resolve built-in global functions and mixins. + ## Draft 5 * Drop the `lighten()`, `darken()`, `saturate()`, `desaturate()`, `opacify()`, diff --git a/accepted/module-system.md b/accepted/module-system.md index 507c82b4..9e0d6c45 100644 --- a/accepted/module-system.md +++ b/accepted/module-system.md @@ -1355,6 +1355,13 @@ type `type`, and an [import context](#import-context) `import`: * Otherwise, if `member-uses` contains a single module, return the member of type `type` named `name` in that module. +* Otherwise, if the implementation defines a global member `member` of type + `type` named `name`, return that member. + + > This includes the global functions and mixins defined as part of the Sass + > spec, and may also include other members defined through the + > implementation's host language API. + * Otherwise, return null. ### Forwarding Modules