chriseppstein/sass — comment on commit 52c9084c1e1258473d00274fbf210d6c44ae14ad
File: doc-src/SASS_REFERENCE.md line 1475
By nimbupani:

- `@silent` does not seem consistent with other SASS functions that are `@` based.

- I cannot think of a usecase where a mixin should be silent given that is not a usecase for mixins. `@silent` seems like a hand-in-glove fit for `@extend` rather than the other way around. And I do not think that would be a major use case.

- I think `@extends` should not be silenced retroactively. It is not like you can declare a mixin retroactively. It either is silent or not. A retro active silencing of an existing class should have no effect. Anything that follows a `@silent` should not be output as CSS.

I think we should try to aim for 80% of the common problems that would be solved with `@silent` directive rather than trying to solve all possible usecases. I feel `@silent` before a selector would be a better fit.