You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, this would be quite burdening since then the plugin would have to parse/evaluate everything after @function till { on it's own (and either loose all of these features or implement them on its own thus turning itself in almost full-featured compiler).
But even w/o above considerations, the answer still would be "just no, sorry". (Less did not use at-rules for its own features for 8 years and I don't see any reason it should suddenly start to do that now. It's already fed enough with @ of variables. Besides there're practical reasons to not abuse at-rules - so it's actually pretty questionable which way is more invasive). So yes, abusing mixins is a hack, but it has its reasons.
Closing as "out of the plugin scope" (The proposal is more suitable to discuss at less/less.js#538. And @function suggestion is already there, though all the con-args remain).
It would be less invasive like sass's
@function
instead of using a scope or a prefix to define the functions.The text was updated successfully, but these errors were encountered: