It really depends on what you mean by “mixin” – everyone seems to have a slightly different idea. The kind of mixin I’d like to see (but which isn’t available in C#) is making implementation-through-composition simple: public class Mixin : ISomeInterface { private SomeImplementation impl implements ISomeInterface; public void OneMethod() { // Specialise just this … Read more
You need to use interpolation (eg. #{$var}) on your variable in order for Sass to treat it as a CSS property. Without it, you’re just performing variable assignment. @mixin w_fluid($property_name, $w_element, $w_parent:16) { #{$property_name}: percentage(($w_element / $w_parent)); }
Mixins are a concept from Lisp. A good explanation from Dr. Dobbs: A mixin is a fragment of a class in the sense that it is intended to be composed with other classes or mixins. […] The difference between a regular, stand-alone class (such as Person) and a mixin is that a mixin models some … Read more
This can be done with macros (that are officially a part of Scala since 2.10.0-M3). Here’s a gist example of what you are looking for. 1) My macro generates a local class that inherits from the provided case class and Persisted, much like new T with Persisted would do. Then it caches its argument (to … Read more
Well, no, you can’t use class name to determine a variable or a return value. So it’s usually done in reverse, for example like this: @brand-default: #649d84; @brand-africa: #df6f20; @brand-nz: #444444; h1 { .brand-colors(); } h2 { .brand-colors(background-color); } .brand-colors(@property: color) { .color(default); .color(africa); .color(nz); .color(@name) { .brand-@{name} & { @value: ‘brand-@{name}’; @{property}: @@value; } … Read more
It’s one of those things that’s just not allowed. The only thing you can do is turn those imports into mixins (import the file outside the @if and call the mixin where appropriate). Clarification: _partial.scss @mixin partial { .test { color: red } // other styles here } styles.scss @import “partial”; @if $someval == true … Read more
Subclass Factory Mixins There is another way to realize mixins in Javascript: With subclass factories. A subclass factory is a function that excepts a base class and returns an extended subclass of this base class: const mixin = base => class extends base { /* properties to mix in */ } Subclass factories are possible … Read more
Mixins is all about how a class does what it does, it’s inheriting and sharing concrete implementation. Interfaces is all about what a class is, it is the abstract signature and promises that the class must satisfy. It’s a type. Take a class that is implemented as class MyList<T> extends Something with ListMixin<T> …. You … Read more
I believe this is impossible to do strictly at runtime, because traits are mixed in at compile-time into new Java classes. If you mix a trait with an existing class anonymously you can see, looking at the classfiles and using javap, that an anonymous, name-mangled class is created by scalac: class Foo { def bar … Read more
Before going into what a mix-in is, it’s useful to describe the problems it’s trying to solve. Say you have a bunch of ideas or concepts you are trying to model. They may be related in some way but they are orthogonal for the most part — meaning they can stand by themselves independently of … Read more