Odd symbol comparison behaviour about ironscheme HOT 5 CLOSED

Thanks! Will check it out.

from ironscheme.

This is caused by boxing behavior in C#. All symbols in IronScheme are interned, hence a reference comparison works.

The best way to do this specific case is to emulate what the compiler does and use SymbolTable.StringToObject(string) or use SymbolTable.Intern(SymbolId).

It might be a good idea though for me to check the parameters for SymbolId type and call that Intern for Eval. I will play with the idea.

from ironscheme.

Good news (and 1 bad).

I can get all of them to return true except for the last.

I suggest you use the workaround with SymbolTable there.

Will make the change tonight and commit and rebuild.

from ironscheme.

Thanks for the fast response and your suggested workaround.

from ironscheme.

Fixed in commit 2716cab

from ironscheme.