Are you using the constant and the changed value breaks your stuff? What about making the new constant private instead?

PsySH extends StringInput for its ShellInput (which basically adds the ability to have a "code" chunk that gets treated literally). It had to implement its owntokenize method and was referencing these two constants, since it had so much in common.

If you don't want this to be part of the public API, it'd make sense to make the new one private. I don't think anyone else was silly enough to use it, but there are a lot of PsySH versions going back years that depend on the previous public constants so let's at least keep them working :)

Thanks for the PR and the details. I'm fine as is :)

Even if it were possible (I'm not sure it is) any more aggressive deprecation than a comment would violate semver.

I mean in 6.1. Either we don't deprecate it at all and we remove that comment or we need a strategy on 6.1 to effectively be able to remove the constant in 7.0. I just don't remember if just adding a@deprecated comment is enough for a constant.

I'm not sure what you normally do, but I found several other comment-only deprecation notes that I modeled this after.

Thank you@bobthecow.

Thank you!