-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The if
function is special: should be lazy.
#107
Comments
Note: One down, n to go. The issue with the |
kaj
added a commit
that referenced
this issue
Jun 1, 2021
Progress: 3727 of 6171 tests passed in dart-sass compatibility mode. * `value::Unit` and `value::ListSeparator` has new alternatives. * The `List` alternative in `sass::Value` and `css::Value` is modified. * The `Use` alternative in `sass::Item` is modified, and `Forward` added. * Most of `@forward` and some more of `@use` is now supported. PR #109 and #110. * Handle unknown units. PR #101. * List can be undecided between beeing comma-separated and beeing space-separated. PR #102. * Improved parameter handling and returned values of the supported selector functions. PR #103. * Implement `meta.module_variables` and `meta.module_functions`. * Implement `math.div` function. * Improved parameter checking for `hwb`, `alpha`, and `invert` functions in `sass:color` module. * Support slash-separated lists. PR #111. * The `if` function evaluates its arguments lazily. Issue #107. * The `--include-path` cli argument is now named `--load-path`. * At least some documentation on all public items. * Update sass-spec test suite to 2021-05-24. Also include "other" files (for `@use` and `@import`) in rust code for the suite. Tested with rustc 1.52.1, 1.50.0, 1.48.0, 1.45.2, 1.53.0-beta.3 (82b862164 2021-05-22), and 1.54.0-nightly (657bc0188 2021-05-31).
@kaj I'm running into this again on master with bootstrap 5.0.1
|
Strange, I seem to get a different error. Are you sure your |
Sorry I forgot about the flag :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
if
function is special in that it's argument should be lazily evaluated. Bootstrap 5 (and probably other common scss code) relies on this.Originally posted by @Keats in #3 (comment)
What happens in the bootstrap compiling error above is that both arguments to the
if
on line 166 is evaluated (even though only the$if-true
one is needed) and evaluating the$if-else
value causes an error.The text was updated successfully, but these errors were encountered: