On Wednesday, 16 July 2014 at 20:11:22 UTC, Johannes Pfau wrote:
I think it's kinda ridiculous that D embedded code will only be
usable
with strong optimization flags, but whatever.
Do you have numbers? Transitive volatility implies you planned to
do very complex things in embedded. If optimizations are so
critical, how do you know if complex code can work without them
due to its sheer complexity even if typeinfos were removed
somehow?
On Wednesday, 16 July 2014 at 20:14:38 UTC, Johannes Pfau wrote:
I'll take this as you pre-approve all the mentioned extensions?
* way to disable typeinfo for struct
BTW, typeinfos are needed for basic types too and not everything
is inline - e.g. array comparison.
* way to disable initializer
* force inlining
* (way to omit copy constructor function / force inline)
We have bugzilla for issues and you can refer to them (with
appropriate severity) to describe a level of support for embedded
(and baremetal). Would be better with numbers to justify severity.
