Proof of concept for v2 - NO duplication, NO `static if` hell, NO difficulty with interoperability

Ola Fosheim Grøstad ola.fosheim.grostad at gmail.com
Fri Nov 5 10:53:17 UTC 2021


On Friday, 5 November 2021 at 06:47:53 UTC, bauss wrote:
> Tbh. the best solution would be ditching Phobos for an entirely 
> new standard library. Like writing it from scratch and when 
> it's stable enough then provide a way of transitioning existing 
> code to the new standard library.

If it was kept smaller maybe. Meaning no xml, json, zip, zlib, 
digest, datetime, curl, odbc, checkedint, function, algorithms, 
sumtype, ranges, etc.

Move all those (same code) to a separate application layer with 
its own versioning.

But before doing anything like that you ought to:

1.  Go through Phobos and find all the language issues that are 
addressed in the Phobos code.

2. Change the language so that a new standard lib does not have 
to account for language weaknesses.

3. Write the standardlib in such a way that it is quite low level 
(everything should be meaningful in the context of embedded 
programming).

4. Identify interdependencies in the current Phobos library.

5. Write a set of "standard" application level libraries on top 
of that (streams/ranges, algorithms, compression, encryption 
etc), split up in such a way that there are no interdependencies 
(4).

It is totally doable. It is a management issue. Mostly political. 
Not so much to do with manpower or technicalities IMHO.





More information about the Digitalmars-d mailing list