Proof of concept for v2 - NO duplication, NO `static if` hell, NO difficulty with interoperability
H. S. Teoh
hsteoh at quickfur.ath.cx
Mon Nov 1 16:40:42 UTC 2021
On Mon, Nov 01, 2021 at 11:39:46AM -0400, Andrei Alexandrescu via Digitalmars-d wrote:
> On 11/1/21 10:09 AM, Ogi wrote:
> > On Sunday, 31 October 2021 at 01:59:38 UTC, Andrei Alexandrescu wrote:
> > > https://github.com/dlang/phobos/pull/8309
> > >
> > > Destroy!
> >
> > Good stuff.
> >
> > Notably absent are `std.range.interfaces`. What are we going to do
> > about them?
>
> I don't think they need particular attention - either publish them as
> they are, change them, or give up on them altogether (I believe
> allowing ref-type ranges was a mistake).
So what do we do with functions that need to return ranges of multiple
types (albeit with compatible element types)? Like std.range.choose
except with a runtime condition. Or functions that return ranges whose
concrete types are not known until runtime?
If classes are not the answer, then what's the alternative?
T
--
They say that "guns don't kill people, people kill people." Well I think the gun helps. If you just stood there and yelled BANG, I don't think you'd kill too many people. -- Eddie Izzard, Dressed to Kill
More information about the Digitalmars-d
mailing list