libc dependency

[Honey via Digitalmars-d-learn]

On Tuesday, 20 June 2017 at 05:19:21 UTC, Cym13 wrote:
> The issue with that is that you assume:
>
> 1) that a complete libc replacement can be created from scratch
> 2) that a correct libc replacement can be created from scratch
> 3) that a better libc replacement can be created from scratch
> 4) that this replacement can be maintained for years to come on 
> all plateforms

For things like core.stdc it would be insane not to depend on 
libc. In fact, it would be strange if we did not call into libc, 
here.

But does this really mean that depending on libc must be the 
default for everyone?

I doubt that we would have to replace every function provided by 
libc. We only have to provide alternatives for what we use. Other 
than that I share your scepsis.

I am not saying that we should actually drop the dependency. I 
was just curious to learn something.