fyi repo reorganization - opend-dmd deleted, opend repo now holds main compiler

[adamdruppe]

The hope is to merge ldc and dmd repos so they update together, this just one step. Should also be easier to fork now too.

[quickfur]

How does this work? ldc will be a separate branch or something? How do you plan to sync with ldc upstream (if at all)?

[adamdruppe]

I'd like the code to be completely merged. Huge chunks of the ldc repo are just checked out dmd repo with some extra patches on top, which is reapplied any time they try to resync and... we can just merge those changes right in.

Yeah it might be a pain with the history being changed to pull from upstream. But I think it will be worth it to simplify things and eliminate a bunch of copying scripts.

[quickfur]

Weird they chose to do it that way. Why didn't they just use version to swap in/out the ldc-specific bits? Ostensibly that's what version is for.

[quickfur]

Whatever way we choose to do it, I'd advise making it such that it's relatively easy to pull changes from ldc upstream. The llvm-specific stuff especially, I don't know if anyone here knows how to deal with. :-D

[adamdruppe]

rumor has it it is because the upstream dmd repo is closed to llvm code but i don't know for sure

[quickfur]

Whatever the case may be, reducing the insane complexity of managing multiple repos in tandem is a good idea IMO. The original idea of splitting dmd, druntime, phobos is in retrospect kinda silly, because many changes depend on exact versions anyway, so you might as well just do a single repo for all of them.

Or, if git submodules don't make you puke, have a main repo that pulls in all the dependents. But yeah, I'd also want to avoid using git submodules if I can help it... it leads to pathological situations quite often, and is more useful for things like pulling an independent 3rd party library rather than an essential component of your main app.

[IgorDeepakM]

Not only that, the delay of all the merging. Imagine if you work mainly on LDC, but you want to change something that affects both DMD and LDC. In that case you have to work on DMD, then do PR and hopefully it will be merged. Then you have to wait until the LDC maintainer synchs with DMD in order for it to get to LDC.

If you work on MAC, you have no choice than to work on DMD but you will do that more blindly as there is no MAC support.

Merging LDC and DMD is a very welcome choice I think.