Derive resolver extensions from the discovery language map #8

New Issue

2026-09-04T20:40:34+02:00

nami-ai commented

2026-09-04 20:40:34 +02:00

Issue #3 fixed the missing extensions by adding RESOLVE_EXTS in src/index/imports.rs, but the supported-extension list is still duplicated: src/config.rs:32-44 defines language_for, while src/index/imports.rs:154-158 maintains a second manual list.

This can regress silently when a new extension is added to discovery but not to module resolution. Keep one shared source of truth (for example, a shared extension table) while preserving the resolver's probe order. Low priority; the current behavior is correct for the present list.

Issue #3 fixed the missing extensions by adding `RESOLVE_EXTS` in `src/index/imports.rs`, but the supported-extension list is still duplicated: `src/config.rs:32-44` defines `language_for`, while `src/index/imports.rs:154-158` maintains a second manual list. This can regress silently when a new extension is added to discovery but not to module resolution. Keep one shared source of truth (for example, a shared extension table) while preserving the resolver's probe order. Low priority; the current behavior is correct for the present list.

endergebnis commented

2026-09-04 20:45:27 +02:00

Fixed in commit a416a9f.

Fixed in commit a416a9f.

endergebnis closed this issue

2026-09-04 20:45:27 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: endergebnis/rustytokens#8