@Florian Diebold I was thinking why not making
&dyn Trait behave like
&impl Trait at least for the short term. Of course, this is not how it works but I'm just wondering if we can close that gap this way until the proper support is implemented?
you mean the other way around?
I don't think it's worth doing, proper
impl Trait support in Chalk isn't far off
Not sure what you mean by "other way around",
impl Trait works fine, while
dyn Trait doesn't...
This is especially palpable since we switched to
only argument position
impl Trait works fine, return position
impl Trait doesn't work at all currently
dyn Trait mostly works fine, just is missing super trait support
which is something that could just be fixed in Chalk
Aha, so this is due to the supertaits...
(it's on my list...)
So, this is the chalk field of responsibility and we cannot put a gag in our code.
it would be harder to work around this in our code than in Chalk