rokucommunity / rokucommunity/brighterscript
thoughts on compiling bs, that interops with _compiled_ bs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
given TodoVM.bs
class TodoVM extends BaseViewModel
where BaseViewModel is a library that I import in my project with compiled sources (i.e. BaseViewModel.brs), how does the compiler know the extend is valid?
I have this currently in my project, so I'm distributing both compiled and uncompiled sources.
I'm also thinking of adding options to turn the class BaseViewModel not found error into a warning; but it got me thinking...
is there some lightweight metadata we can bundle in comments at the bottom of a file, or something similar to d.ts file, which the compiler can read, to not lose important information when encountering compiled sources.
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 with the compiler behavior around TodoVM.bs extending BaseViewModel from the compiled BaseViewModel.brs example. Trace how class resolution handles compiled sources, then define the metadata or warning behavior needed so the compiler preserves enough information to validate the relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100