Porting std.typecons to Phobos 3

Paul Backus snarwin at gmail.com
Sun Nov 17 12:51:44 UTC 2024


On Sunday, 17 November 2024 at 10:51:27 UTC, Adam Wilson wrote:
> We do have to be mindful of time as there are a ton of 
> modules/types to get through and very limited labor pool but 
> beyond that we're here to build the best version of Phobos we 
> can. If that means redesigning then that's what we do. JMD has 
> already done a ton of redesign work on Traits.

Is there any place where interested parties can check on the 
current state of Phobos 3 development, and find out which 
modules/types are in-progress vs. up for grabs? If not, it might 
be a good idea to create one--maybe a Github projects page, like 
the one in [this recent announcement][1].

[1]: 
https://forum.dlang.org/thread/pzrsrbwcdnysdgbyjijq@forum.dlang.org

> As far as `Tuple` is concerned, Timon is working on building 
> them into the language so that we don't need to worry about it. 
> Apparently the implementation is done, he just needs to do the 
> PR and DIP for it. We've been discussing on Discord whether or 
> not to port the Phobos tuples at all.

Built-in tuples for Phobos 3 would be awesome! If they support 
named fields, then there's definitely no reason to keep Phobos 
`Tuple` around IMO. If not, there might be room in Phobos 3 for a 
`NamedTuple` type (a la Python).


More information about the Digitalmars-d mailing list