H1 2015 Priorities and Bare-Metal Programming

[Mike via Digitalmars-d]

On Sunday, 1 February 2015 at 11:22:04 UTC, Johannes Pfau wrote:
>
> So I'd say there are not too many language problems, the main 
> problem
> is runtime/compiler interaction:
>
> * If you don't want to use any runtime at all that's actually 
> the
>   easier part. We'd need to implement a little more of betterC 
> but this
>   can be done easily. Mike would prefer the compiler to 
> autodetect the
>   capabilities of the runtime (implemented hooks) instead of 
> compiler
>   switches. That'd be better but some more work.
>
> * Using only part of druntime is ugly. The one thing most 
> people would
>   probably like to strip out is the GC, but keep exception 
> handling,
>   threads, ... But the GC is everywhere: core.demangle doesn't 
> work
>   without, backtraces, exceptions, threads. Right now you 
> either use
>   all of druntime or nothing but it's not possible to use parts 
> of
>   druntime only, it's not modular enough.

Yes, I totally agree with this assessment.

Mike