Parser priorities2

Don't review it. I'm just trying to test it.
Okay but if you're not modifying them, then why not make them immutable?

Sorry, this just introduces the potential for a really nasty bug that I
don't want us to have to deal with later. It's way too easy for a developer
to not realize this constraint, make a change, and introduce a bug that is
very hard to track down. I'm not satisfied with a partial solution to this,
not in this case.


On Wed, Jun 11, 2014 at 1:31 PM, Radu Mereuta <notifications@github.com>
wrote:

> In src/javasources/KTool/src/org/kframework/kil/TermCons.java:
>
> > @@ -140,6 +156,18 @@ public boolean equals(Object obj) {
> >      }
> >
> >      @Override
> > +    public int hashCode() {
>
> I fixed the bug, and it still works, and it works because I'm not
> modifying TermConses after I creating them. Without immutable objects, I
> don't think there is a safe caching mechanism for hashCode().
>
> Anyway, any more comments?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kframework/k/pull/455/files#r13665685>.
>