PistonDevelopers / PistonDevelopers/dyon
Add `check__in_string_imports`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 56
- Avg merge
- 1m
- Merged PRs (30d)
- 6
Description
Sometimes it is nice to use Dyon scripts to analyze Dyon code. The lifetime/type checker has a lot of useful knowledge about the source that currently is not available for Dyon scripts.
For example:
- which functions are called
- from where functions are called
- the type of an expression in the code
- the parent/child relationships of expressions
- the kind of an expression (call, call argument, loop etc.)
By adding a check__in_string_imports, scripts can access the knowledge that the lifetime/type checker has about the source at the end of inference.
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 reading the lifetime/type checker and the inference stage, focusing on what checker knowledge is available at the end of inference. Define how check__in_string_imports should expose called functions, call origins, expression types, parent/child relationships, and expression kinds to Dyon scripts; done means scripts can access this information from analyzed Dyon source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100