shorter mixin call

[bmargogne]

Hi. This is a suggestion more than an issue but I am not sure of where to suggest it ...

Would it be possible to call mixins using a syntax such as

@mixinName( ... )rather than @include mixinName( ... )?

That would be a lof of typing saved !

Thank you for the great work.

[joneff]

Just for the sake of argument, lets imagine you have a mixin called media. How would the compiler know when you want to use media queries and when to use your mixin?

I'd welcome shorter mixins calls, as long as they are still explicit enough, do not interfere with css syntax and are not magical.

[bmargogne]

Hello, and thank you for your reply.

I am not an experienced developper, so I will surely not have an
argument with you :)

I didn't think this would be a serious issue : I thought such new
writing convention would imply a list of forbidden mixin names (extends,
include, media...), just like any other language do (I guess names like
'function' or 'class' are forbidden in many languages).

I do not really know all implications apparently !

have a nice day.

Le 07/11/2016 à 13:17, Иван Жеков a écrit :

Just for the sake of argument, lets imagine you have a mixin called
|media|. How would the compiler know when you want to use media
queries and when to use your mixin?

I'd welcome shorter mixins calls, as long as they are still explicit
enough, do not interfere with css syntax and are not magical.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2178 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/ALuPtSP9H1eaBsja9nJoR2ZM-AR3uZGWks5q7xbugaJpZM4KjWJn.

Bertrand MARGOGNE
+33 6 99 55 75 43

[long-lazuli]

What about @(mixinName) { ... } or simply take the Sass syntax +mixinName { ... }.
But I this has been already discussed...
#366

[joneff]

You are right. This thread should be closed.

/cc @chriseppstein