Jonathan Lindegaard Starup
Jonathan Lindegaard Starup
Too annoying to add for now with the backend dependence on monotype instead of backendType
@magnus-madsen I think this highlights a scary case for resilient compilation - if I introduce a new module around some code, many of my functions are not found. All of...
I guess so yeah, but we can check and see if this example is faster then
@jaschdoc maybe relevant to you
Is this opening the door to compiler generated functions :O Previously we've only done this through traits. e.g. here you would add a compiler generated instance for `ToExt`. We don't...
But ToFromExtVar could be a trait with compiler defined instances - I think we should consider that since it is how we usually do these things
> Can it? This works for closed rows ``` trait ExtVarConv[t] { type ExtVarRep[t] : Type def toExtVar(x: t): ExtVarRep[t] def fromExtVar(x: ExtVarRep[t]): t } instance ExtVarConv[Animal[a]] { type ExtVarRepr[Animal[a]]...
Shouldn't it look like a labeled argument? Or do you mean a argument with default?
Hmm I suppose. But I'd also like `def fun(_: {param = t}): ...` or something less subtle like that. It's mostly that I don't want type type `param.param` everywhere in...
There is no `HashSet`, only `MutHashSet`