Bulby
Bulby
Kotlin allows the paramaters to be put in the class header ``` EnergyStoragePlugin(private val energyStorage: EnergyStorage) ```
I prefer either Noise or None. Noise is used by tink, while None is used by python (and I prefer it when making interpreters)
None is not synonymous with Void; Void is the absence of a value; It has nothing, and cannot be used as a value. None is a value with no meaning....
> ```hx > enum abstract NoUse(Null) from Dynamic { > var NoUse = null; > } > > class Test { > static function main() { > var x:NoUse =...
the `None` type is supposed to be a type that has no meaning, I don't see the harm in letting it unify. The only use I can think of is...
oh dear. runners up for me would be `Nothing`, `NoUse`.
I do think it should be compile time and that was what I was intending. I don't even know how it would happen on runtime.
Now that I think about, maybe it's unwise to not have a "true" function. I'd say maybe we could make a function that uses optional parameters but that isn't fully...
How would variance affect things? Simply doing how it already works, by "downgrading" (taking a subclass and removing all its properties that make it different from its parent) should work.
Are you even allowed to have an two interfaces with functions of the same name? That seems silly. My specification says interfaces can't have overload functions and thus this should...