Iain Buclaw
Iain Buclaw
> I'd just go the simpler route of making Bugzilla read-only once the data has been moved to github. I've done this for gdc bugzilla before, based off http://toolsmiths.blogspot.com/2008/05/making-bugzilla-read-only.html 1....
Shouldn't this be an issue under ldc? Why is it a project here?
Half this information is outdated / partially irrelevant. 1. Bugzilla is here: https://gcc.gnu.org/bugzilla/buglist.cgi?component=d&product=gcc 2. How is one supposed to get in touch with the development team via a wiki? 3....
@Laeeth, that could be a project in its own right, feel free to assign me to that if one is created. I'll think about gdc tasks tomorrow, though right now...
> If I understand correctly, when this switch is enabled, code that uses `cfloat`, `cdouble` and `creal` will instead treat them as `float`, `double`, `real`? No, `cfloat`, `cdouble`, and `creal`...
Removing a feature is still a new feature... :-) If complex numbers get removed outright, then the `-preview=complex` will turn into a `-revert=complex` for another couple years.
> Is it close to being done? The implementation is "done", just slowly rolling out the scaffolding for the library support. It would be good to get `-transition=complex` being enabled...
> bash: line 6: nproc: command not found It's `sysctl -n hw.ncpu` on OpenBSD (and NetBSD likewise) https://github.com/D-Programming-GDC/gcc/blob/4bd3c9a4fcbda91e3cb425434e8ee3c7e9acfc22/buildci.sh#L81
> > It would be good to get -transition=complex being enabled by default before this as well, so that complex types are in full deprecation mode. > > It would...
@WalterBright there is no cross-module inlining in single-module compilation. There are a couple tricks to help it though. For example, `pragma(inline)` functions are lazily codegen'd into every module that references...