Daniel Oberhoff
Daniel Oberhoff
Looking at the actual implementation of an array it does not seem safe to pass around slices. for that to be safe you would some kind of copy-on-write semantics...
ah, I was wrong it is quite safe. so yes, in theory at least all const array arguments could easily be turned into slice arguments.
Yes, because create is used as codegened name for the function, at least for classes. It was likely done like this to mimic what is done in serenity in many...
sorry for abusing the CI to fix my code...its gotten too late. will try not to be that lazy next time :). finally builds now.
just curious: would it be thinkable not to have to state `implements` in the implementing classes? Then a trait requirement would always be fulfilled if the given method(field) exists, thus...
There are/will be requires clauses? Ok, i always thought traits are an alternative
Basically the same as with recursive enums which have to be boxed (aka class)
only if it is a struct, it should work for classes.
i.e. this should be ok: ``` class S { field: S } ```
Wasn't this already implemented?