Removing ISSUE! from the ANY-WORD! category

[hostilefork]

Because binding is involved in this...I'll point out this thread, where the question of relationship between strings and binding is raised:

Could strings have context?

A common problem faced within Rebol is passing string-based templates to functions without any context attached to them. What would it take/cost to add context to string values? An example: my-context: make object! [ x: 10 template: "x" ] reduce load my-context/template The thought would be a string in source would adopt its parent context, otherwise would be unbound.

If you're writing a preprocessor system you might argue that you'd want some context information along with #foo. But off the top of my head, there are more pressing examples where templatize {some $(foo) and $(bar)} would like to be able to know what foo and bar you mean, without having to pass those in explicitly as templatize/with {some $(foo) and $(bar)} [foo bar].

Just doesn't seem to make sense that ISSUE! should be an ANY-WORD!, when precedent clearly favors #123 being an ISSUE!, and it having string-like properties. If new ideas come along that make it easier to associate bindings with strings, that would be a good development. And we should be open to how such tricks could be done. But if those ideas don't come, I don't see what makes ISSUE! picked as a word type to be the exception to the rule.