Throw compile time errors for dangling identifiers.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Description
When a user code contains some identifiers(variable names, functions...) that aren't defined anywhere in the source. We should be able to throw a compile time error(dev time error).
This is possible because we currently do collect all dangling identifiers
then,
- only import the ones available in an adaptor
- whitelist the ones present in our supported globals.
- coming soon.... whitelist the ones provided by our globals file.
Any dangling identifier that survives these passes is 99% likely to cause a runtime error.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the compiler's dangling-identifier collection and the adaptor and supported-global whitelist passes described in the issue. Determine how the remaining identifiers can be reported during compilation, then add coverage showing that unresolved names fail before runtime while adaptor and whitelisted globals remain valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100