Integer key based indexer is omitted when string key based indexer exists in interfaces about jint HOT 7 CLOSED

Now indexer selection knows how to prioritize better and latest issue should be covered by #1669

from jint.

Should be now fixed in main / soon available on MyGet feed.

from jint.

Should be now fixed in main / soon available on MyGet feed.

This issue remains in version 3.0.0-preview-506(Myget feed). @lahma

from jint.

Should be now fixed in main / soon available on MyGet feed.

This issue remains in version 3.0.0-preview-506(Myget feed). @lahma

The test case associated with the PR now passes and earlier it didn't resolve to integer indexer. Can you show a failing test case to diagnose?

from jint.

Should be now fixed in main / soon available on MyGet feed.

This issue remains in version 3.0.0-preview-506(Myget feed). @lahma

The test case associated with the PR now passes and earlier it didn't resolve to integer indexer. Can you show a failing test case to diagnose?

Just remove line 3300 of Jint.Tests/Runtime/InteropTests.cs:

        public interface IStringCollection : IIndexer<string>, ICountable<string>
        {
            string this[string name] { get; }
            string this[int index] { get; } // remove this line
        }

because interface "IStringCollection" inherits "IIndexer" which claims the integer indexer above.

from jint.

Inherited indexer that needs type coercion might be a limitation I'd be willing to accept, unless someone wants to submit a PR to improve the logic.

from jint.

Now indexer selection knows how to prioritize better and latest issue should be covered by #1669

Kudos to you for your exceptional PR! Your expertise and attention to detail are highly appreciated.

from jint.