The Halide ur-project wants to use the name “halogen” for an upcoming project #1
Description
As is evidenced by this comment by @zvookin on Halide PR3108:
We have plans for the name "Halogen" in the Halide context to be a library of generators that are part of the project. I realize we can't make a claim on the name so it is more asking a favor than a requirement, but I'd like to use this name for what is effectively our standard library of useful packages for the language. We're way overdue to get that started of course...
… naturally, I love halide – or why else would I fritter away my time building a project that stands atop it? – and I would like to hand over the “halogen” name to them for their use, if and when it makes sense to do so.
The main problem with that is, since it is the entire name of this entire thing, it appears scattered and viscerally embedded throughout all of all the code in all the history, like it was blasted into it with a blunderbuss. It is going to be task of high-magnatude suck to lexically disentangle the name from that which the name names.
Furthermore, I will be in need of a name with which it’ll be replaced – preferably one of equivalent relevance and awesomeness. Which that is a tall order; consider my reply to @zvookin’s comment:
@zvookin I knew it – I knew “halogen” was too good to be untaken! I remember starting that project and thinking “halide generators… OK… halogen?” (because I too enjoyed chemistry in eighth grade), searching the codebase and Google and subsequently being genuinely shocked that no one else had laid claim to it.
So then – henceforth, I welcome any and all project name suggestions, tips, notions, and ideas, from anyone anywhere anytime, that land somewhere along the lines of all this. Yes!