Phobos 3 Discussion Notes - 02-01-2024

[Martyn]

On Friday, 2 February 2024 at 09:09:37 UTC, Adam Wilson wrote:
> Walter and I had a productive conversation yesterday about 
> Phobos 3 and we felt it would be appropriate to share some 
> notes on our discussion.
>
> Snip...
>
> Finally, we touched briefly on the major changes we would like 
> to see in Phobos 3 and these are the major changes we are 
> committing to for Phobos 3 so far:
> - Removal of Autodecoding.
> - Promoting allocators out of experimental.
> - Range interface redesign (see JMD's thread 
> [here](https://forum.dlang.org/thread/mailman.588.1705813271.3719.digitalmars-d@puremagic.com)).
> - Fix std.traits.
>
> The above list is not exhaustive and we are open to further 
> suggestions. For myself, I would love to see Cryptography and 
> Stream API's make it into Phobos, but I am sure that the list 
> of what the community wants to add is legion so those could end 
> up being lower priority.
>
> Snip...
>
> If you would like to participate in the design discussion on 
> Phobos 3, I am currently hosting a repo on my GitHub with GH 
> Discussions for unresolved/undesigned topics, and PR's for 
> editing the actual design document. Link is here: 
> https://github.com/LightBender/PhobosV3-Design

Very interesting!

I really like the Allocator idea. Something I think will benefit 
D and is overdue if being honest.

Curious to know how this will work for D. Will Allocators be 
available for BetterC as well? I certainly hope so!

If so, I guess the **default** Allocator will be the GC one, and 
can still be disabled. Being able to change the default (or 
change locally like in a function or pass it as parameter) would 
provide a lot of flexibility.

It's just I see possiblities of BetterC being able to use certain 
features that are not available, like dynamic or associative 
arrays. To be designed for allowing us to specify the Allocator 
to use (or default if not specified at all) and it doesn't need 
to be a GC one gives the programmer a lot of control for low 
level as well as high.